> For the complete documentation index, see [llms.txt](https://docs.bloombot.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloombot.app/manager/pages/tasks/solana/social.md).
# Social
{% hint style="info" %}
Social Tasks automate trades based on social activity, including Fomo/Pump.fun callouts and Twitter signals. Six different modes track specific signals and automatically trigger buys or sells.
***
**Before you start**
* Set a Social default wallet in the Wallets page under Trading Modes.
{% endhint %}
#### Create Social Task
Six modes are selectable from the tabs at the top of the Create Social Task modal:
* **CA Scanner**: triggers the task when a contract address appears in a tweet from the tracked account.
* **Engagement**: triggers the task when the tracked account replies to, retweets, or quote-tweets a specific tweet.
* **Follow / Unfollow**: triggers the task when an account follows or unfollows another user.
* **Posts & Replies**: triggers the task when the tracked account posts, replies, retweets, or quote-tweets.
* **Tweet Delete**: triggers the task when a specific tweet is deleted by its author.
* **PF Callout**: triggers the task when a tracked Pump.fun caller calls out a token.
{% tabs %}
{% tab title="CA Scanner" %}
Buys contracts posted by the tracked account in tweets, retweets, replies, or quotes
| Field | Description |
| ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Wallet** | Wallet used for the task. |
| **Config Name** | Custom name for this task. |
| **Target Handle** | Twitter handle to track. URL or username without the @. |
| **Amount** | Amount spent per buy. |
| **Target Actions** |
Trigger type:
Tweet: original posts.
Retweet: reposts. Contract taken from the original post.
Reply: replies with a contract.
Quote: quote-tweets with a contract.
|
| **Max Buy Count** | Maximum contracts the task will buy. Set to 1 for the first only, 2 for the first two, and so on. Changing the target does not reset this counter. |
| **Use OCR** | Detects and buys contracts from images posted by the target account. |
**Task Timing**
| Field | Description |
| -------------- | ---------------------- |
| **Enable at** | Task start time (UTC). |
| **Disable at** | Task end time (UTC). |
**Token Filters**
| Field | Description |
| ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| **Min Market Cap** | Minimum market cap required at the moment of the post. Below threshold, the buy is skipped. |
| **Max Market Cap** | Maximum market cap allowed at the moment of the post. Above threshold, the buy is skipped. |
| **Min Age** | Minimum time since token creation. Unit selectable from the dropdown (minutes, hours, days). For Pump.fun migrated coins, counted from bonding. |
| **Max Age** | Maximum time since token creation. Unit selectable from the dropdown. For Pump.fun migrated coins, counted from bonding. |
**Fee Settings**
| Field | Description |
| ----------------- | -------------------------------------------------------------------------------------------------------------------- |
| **Slippage** | Buy slippage percentage. |
| **Priority Fee** | Transaction fee for the buy order. |
| **Processor Tip** | Tip to prioritize inclusion in the next block. |
| **Anti MEV** | MEV protection against sandwich attacks. |
| **Auto Tip** | Uses the recommended Jito tip automatically. Priority fee stays fixed since the tip is what matters for Jito Blocks. |
**Platforms**
Restrict the task to specific token platforms. Use Select All or Deselect All to toggle the entire list, or pick individual platforms.
**Strategies**
Attach strategies to this task. Click Create Strategy to add a new strategy, then Create Limit Order inside any strategy to add an order. See the **Create Strategy** page for the full configuration reference.
{% endtab %}
{% tab title="Engagement" %}
Triggers a buy when the tracked account replies to, retweets, or quote-tweets a specific tweet.
| Field | Description |
| ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Wallet** | Wallet used for the task. |
| **Config Name** | Custom name for this task. |
| **Target Handle** | Handle of the account whose interactions you want to track. |
| **Target Tweet ID** | ID of the tweet to monitor. |
| **Token Address** | Contract address of the token to buy. |
| **Amount** | Amount spent per buy. |
| **Target Actions** |
Trigger type:
Reply: target replies to the tweet.
Retweet: target retweets the tweet.
Quote: target quotes the tweet.
|
| **Max Buy Count** | Maximum buys the task will execute. Changing the target does not reset this counter. |
**Task Timing**
| Field | Description |
| -------------- | ---------------------- |
| **Enable at** | Task start time (UTC). |
| **Disable at** | Task end time (UTC). |
**Fee Settings**
| Field | Description |
| ----------------- | -------------------------------------------------------------------------------------------------------------------- |
| **Slippage** | Buy slippage percentage. |
| **Priority Fee** | Transaction fee for the buy order. |
| **Processor Tip** | Tip to prioritize inclusion in the next block. |
| **Anti MEV** | MEV protection against sandwich attacks. |
| **Auto Tip** | Uses the recommended Jito tip automatically. Priority fee stays fixed since the tip is what matters for Jito Blocks. |
**Strategies**
Attach strategies to this task. Click Create Strategy to add a new strategy, then Create Limit Order inside any strategy to add an order. See the **Create Strategy** page for the full configuration reference.
{% endtab %}
{% tab title="Follow / Unfollow" %}
Triggers a buy or sell when an account follows or unfollows another user.
| Field | Description |
| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Wallet** | Wallet used for the task. |
| **Config Name** | Custom name for this task. |
| **Follower Account** | Handle of the account whose follow activity you want to track. |
| **Followed Account** | Handle of the account being followed or unfollowed. Set to trigger only when the Follower Account follows or unfollows this specific user. |
| **Token** |
• Custom: buy or sell the token address you enter. • Bio CA: buy the first contract address in the followed account's bio, read when the follow happens.
|
| **Direction** |
Buy to open a position.
Sell to close one.
|
| **Amount** | Amount spent on the buy, or amount of token sold. |
| **Target Actions** |
Trigger type:
Follow: Follower Account follows a new user.
Unfollow: Follower Account unfollows a user.
|
| **Max Buy Count** | Maximum trades the task will execute. Changing the target does not reset this counter. |
| Min Followers | Only buy when the followed account has at least this many followers. Leave empty or 0 for no minimum. |
**Task Timing**
| Field | Description |
| -------------- | ---------------------- |
| **Enable at** | Task start time (UTC). |
| **Disable at** | Task end time (UTC). |
**Fee Settings**
| Field | Description |
| ----------------- | -------------------------------------------------------------------------------------------------------------------- |
| **Slippage** | Slippage percentage for buys. |
| **Priority Fee** | Transaction fee for the order. |
| **Processor Tip** | Tip to prioritize inclusion in the next block. |
| **Anti MEV** | MEV protection against sandwich attacks. |
| **Auto Tip** | Uses the recommended Jito tip automatically. Priority fee stays fixed since the tip is what matters for Jito Blocks. |
**Strategies**
Attach strategies to this task. Click Create Strategy to add a new strategy, then Create Limit Order inside any strategy to add an order. See the **Create Strategy** page for the full configuration reference.
{% endtab %}
{% tab title="Posts & Replies" %}
Triggers a buy or sell when the tracked account posts, replies, retweets, or quote-tweets.
| Field | Description |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Wallet** | Wallet used for the task. |
| **Config Name** | Custom name for this task. |
| **Target Account** | Handle of the account whose posting activity you want to track. |
| **Original Poster** | Handle of the original poster of the tweet being interacted with. Filters replies, retweets, and quotes to those that involve this poster's tweets. |
| **Token Address** | Contract address of the token to buy or sell. |
| **Direction** |
Buy to open a position.
Sell to close one.
|
| **Amount** | Amount spent on the buy, or amount of token sold. |
| **Target Actions** |
Trigger type:
Reply: Target Account replies.
Retweet: Target Account retweets.
Quote: Target Account quote-tweets.
Tweet: Target Account posts an original tweet.
|
| **Max Buy Count** | Maximum trades the task will execute. Changing the target does not reset this counter. |
**Text Keywords**
Filter triggers to tweets whose text matches the configured keyword lists. Expand to set inclusion and exclusion keywords.
**Task Timing**
| Field | Description |
| -------------- | ---------------------- |
| **Enable at** | Task start time (UTC). |
| **Disable at** | Task end time (UTC). |
**Fee Settings**
| Field | Description |
| ----------------- | -------------------------------------------------------------------------------------------------------------------- |
| **Slippage** | Slippage percentage for buys. |
| **Priority Fee** | Transaction fee for the order. |
| **Processor Tip** | Tip to prioritize inclusion in the next block. |
| **Anti MEV** | MEV protection against sandwich attacks. |
| **Auto Tip** | Uses the recommended Jito tip automatically. Priority fee stays fixed since the tip is what matters for Jito Blocks. |
**Strategies**
Attach strategies to this task. Click Create Strategy to add a new strategy, then Create Limit Order inside any strategy to add an order. See the **Create Strategy** page for the full configuration reference.
{% endtab %}
{% tab title="Tweet Delete" %}
Triggers a buy or sell when a specific tweet is deleted by its author.
| Field | Description |
| ------------------- | ----------------------------------------------------------------------------------------- |
| **Wallet** | Wallet used for the task. |
| **Config Name** | Custom name for this task. Auto-generated and editable. |
| **Tweet URL or ID** | URL or numeric ID of the tweet to monitor for deletion. |
| **Token Address** | Contract address of the token to buy or sell. |
| **Direction** |
Buy to open a position.
Sell to close one.
|
| **Amount** | Amount spent on the buy, or amount of token sold. |
| **Max Buy Count** | Maximum trades the task will execute. |
**Task Timing**
| Field | Description |
| -------------- | ---------------------- |
| **Enable at** | Task start time (UTC). |
| **Disable at** | Task end time (UTC). |
**Fee Settings**
| Field | Description |
| ----------------- | -------------------------------------------------------------------------------------------------------------------- |
| **Slippage** | Slippage percentage for the order. |
| **Priority Fee** | Transaction fee for the order. |
| **Processor Tip** | Tip to prioritize inclusion in the next block. |
| **Anti MEV** | MEV protection against sandwich attacks. |
| **Auto Tip** | Uses the recommended Jito tip automatically. Priority fee stays fixed since the tip is what matters for Jito Blocks. |
**Strategies**
Attach strategies to this task. Click Create Strategy to add a new strategy, then Create Limit Order inside any strategy to add an order. See the **Create Strategy** page for the full configuration reference.
{% endtab %}
{% tab title="PF Callout" %}
Triggers a buy or sell when a tracked caller calls out a token.
| Field | Description |
| ------------------- | --------------------------------------------------------------------------------------------------------- |
| **Wallet** | Wallet used for the task. |
| **Config Name** | Custom name for this task. |
| **Pump.fun caller** | The pump.fun caller to follow: a username, a wallet, or a profile link. Their callouts trigger this task. |
| **Direction** |
Buy to open a position.
Sell to close one.
|
| **Amount** | Amount spent on the buy, or amount of token sold. |
| **Max Buy Count** | Maximum trades the task will execute. Changing the target does not reset this counter. |
**Text Keywords**
Filter triggers to callouts whose text matches the configured keyword lists. Expand to set inclusion and exclusion keywords.
| Field | Description |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Keyword Match** |
How a keyword is compared against the callout text:
Partial: matches when the keyword appears anywhere inside the text.
Exact: matches only when the keyword appears as a whole word.
|
**Task Timing**
| Field | Description |
| -------------- | ---------------------- |
| **Enable at** | Task start time (UTC). |
| **Disable at** | Task end time (UTC). |
**Token Filters**
| Field | Description |
| ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| **Min Market Cap** | Minimum market cap required at the moment of the callout. Below threshold, the trade is skipped. |
| **Max Market Cap** | Maximum market cap allowed at the moment of the callout. Above threshold, the trade is skipped. |
| **Min Age** | Minimum time since token creation. Unit selectable from the dropdown (minutes, hours, days). For Pump.fun migrated coins, counted from bonding. |
| **Max Age** | Maximum time since token creation. Unit selectable from the dropdown. For Pump.fun migrated coins, counted from bonding. |
**Fee Settings**
| Field | Description |
| ----------------- | -------------------------------------------------------------------------------------------------------------------- |
| **Slippage** | Slippage percentage for the order. |
| **Priority Fee** | Transaction fee for the order. |
| **Processor Tip** | Tip to prioritize inclusion in the next block. |
| **Anti MEV** | MEV protection against sandwich attacks. |
| **Auto Tip** | Uses the recommended Jito tip automatically. Priority fee stays fixed since the tip is what matters for Jito Blocks. |
**Platforms**
Restrict the task to specific token platforms. Use Select All or Deselect All to toggle the entire list, or pick individual platforms.
**Strategies**
Attach strategies to this task. Click Create Strategy to add a new strategy, then Create Limit Order inside any strategy to add an order. See the **Create Strategy** page for the full configuration reference.
{% endtab %}
{% endtabs %}
***
#### Mass Create
Create multiple tasks at once by pasting a list of handles. One task is created per handle, all sharing the same configuration. Mass Create supports five modes: **CA Scanner**, **Engagement**, **Follow / Unfollow**, **Posts & Replies** and **PF Callout**. Tweet Delete is not available in Mass Create because it requires a specific tweet identifier.
{% stepper %}
{% step %}
**Handles.** Open the **Mass Create Social Task** modal and select the mode from the tabs at the top. Paste handles into **Target Handles**, one per line. The **Valid** counter shows recognized entries. Click Next.
{% endstep %}
{% step %}
**Configuration.** Configure the fields as for a single task (see the sections above). Click Create Task to create one task per valid handle.
{% endstep %}
{% endstepper %}
***
#### Tasks Tab
Tasks appear in the Tasks tab organized by feature.
| Button | Description |
| ---------------- | ---------------------------------------------------- |
| **Start All** | Activates all tasks in the current tab. |
| **Stop All** | Deactivates all tasks in the current tab. |
| **Start / Stop** | Activate or deactivate a single task. |
| **Edit** | Modify a task's parameters. |
| **Duplicate** | Create a copy of a task with the same configuration. |
| **Delete** | Remove a task permanently. |
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.bloombot.app/manager/pages/tasks/solana/social.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
