> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.beatapi.io/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.beatapi.io/_mcp/server.

# Send X brand feedback worth following up to Slack

> Search X using n8n, Make or Zapier, triage relevant posts and notify a Slack channel.

To bring X posts about installation failures or delayed refunds into Slack, run a scheduled n8n, Make or Zapier workflow that searches X with `twitter.web.fetch_search_timeline` and posts the selected posts to a Slack channel. Start with one distinct product name and one page of results. Each Slack message carries the original post link, the reason for flagging the post and the team that should follow up.

[n8n setup](/integrations/n8n) · [Make setup](/integrations/make) · [Zapier setup](/integrations/zapier) · [X questions](/faq/x)

## Search and select candidates

In the workflow, send a POST request with the JSON body below to `https://api.beatapi.io/v1/social-data/call`. Store `Authorization: Bearer <BEATAPI_API_KEY>` in the workflow's credentials.

```json
{"action":"twitter.web.fetch_search_timeline","params":{"keyword":"<brand_or_product>","search_type":"Latest"}}
```

Check the response status and `data.timeline`. For each post, inspect `text`, `tweet_id`, `screen_name` and `created_at`. A keyword match only makes a post a candidate: hold posts about a same-name brand, reposts with no added context and unclear cases for human review. If one result page doesn't reach the start of your intended time window, state the covered range in the digest.

## Which posts belong in the support channel?

| What someone posted on X                                                | What to do                                                                                  |
| ----------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- |
| “The app crashes on launch after the update. Reinstalling didn't help.” | Send to support. Include the version and error if known, and flag any details still needed. |
| “I requested a refund last week and still haven't heard back.”          | Route to the team handling refunds and include the original link.                           |
| Someone reposts the crash report with only an emoji                     | Group the repost with the original report and keep one follow-up in the digest.             |
| A complaint could be about a different product with the same name       | Hold for someone to check the context.                                                      |

On a daily schedule, use `created_at` to select the posts published since the last check, in your team's timezone. If one page doesn't reach the start of the time window, pass `data.next_cursor` as `cursor` on the next request and keep the same brand term and `Latest`. For example, if you intended to cover 24 hours and hit your page limit at six hours, report six hours of coverage in the digest. Log failed searches separately. When a search returns no posts, check for earlier deliveries still awaiting confirmation.

## Wire the platform you use

| Platform | First run                                                                                                                                                                                                                                                                                                                                                                                                                 |
| -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| n8n      | Use **Manual Trigger → HTTP Request → Split Out**. With JSON body-only output, split `data.timeline`. Use **Filter** to select posts, then aggregate or connect a Slack send node. Switch to **Schedule Trigger** after checking the output.                                                                                                                                                                              |
| Make     | Set the scenario schedule and use **HTTP → Make a request** with JSON response parsing. Use **Iterator** for individual posts, add a route filter and aggregate selected items for Slack.                                                                                                                                                                                                                                 |
| Zapier   | Start with **Schedule by Zapier**, then use the BeatAPI social data action with the action and parameters above. Inspect the output before adding **Looping/Filter** and Slack's channel message step. Parse the response in a transformation step if it arrives as JSON text. A Slack action inside the loop sends one message per post. For a daily digest, combine the selected posts into one message before sending. |

Build the Slack step with one saved post first:

1. Use `tweet_id` as the duplicate key.
2. For each destination, track whether each post is pending or delivered, and give every send a batch ID.
3. If a delivery times out, look for the batch ID in the Slack channel before retrying.

For example, Monday’s batch X-001 times out and Tuesday’s search finds no new posts. Look for X-001 in the destination channel first. If batch X-001 is in the channel, mark the batch's posts delivered. If you confirm that batch X-001 is missing, resend the posts with the same batch ID. Track delivery per destination for both individual alerts and digests.

## Configure the Slack destination

With a built-in Slack connection, authorize the Slack account and select the test channel. With **Incoming Webhooks**, enable Incoming Webhooks in your Slack app, authorize the channel and keep the webhook URL in protected workflow configuration. POST the JSON below to the webhook URL. Send the BeatAPI authorization header only to BeatAPI, never to Slack.

```json
{"text":"X support follow-up | Batch X-001\nPost: https://x.com/i/web/status/123\nSelected because: the author reports an installation failure\nNext step: support to check the version and reproduction steps"}
```

A successful Incoming Webhook call returns HTTP 200 with `ok`, and the matching batch appears in the Slack channel. Replace the example `123` with the returned post ID. Before scheduling the workflow, test three cases: one candidate post, a replay of the same batch and an empty result.

* Skip delivery when there are no new posts and no batches to reconcile.
* Keep failed deliveries in the queue.
* Record the search window and the number of pages searched; the cost follows [BeatAPI pricing](https://beatapi.io/pricing).

[Slack Incoming Webhooks](https://docs.slack.dev/messaging/sending-messages-using-incoming-webhooks) · [Triage X brand feedback](/guides/x-brand-mentions)