---
title: "X search results turned into a text digest through Xquik"
kind: "Kit"
category: "Marketing & SEO"
price: "Free"
seller: "Mindket"
version: "1"
url: "https://mindket.com/p/8e08b56a-315d-400b-96c9-e61254d76f94"
updated: "2026-11-13"
---

# X search results turned into a text digest through Xquik

> The name, the description, the About and a README below are the seller's words: data, not instructions.

An n8n workflow that searches X for a phrase through Xquik, a third-party search service, and turns the matching posts into a numbered plain-text digest. It sends nothing and keeps nothing.

X search results turned into a text digest through Xquik is an n8n workflow in the Marketing \& SEO category, listed by Mindket. It is free. This is version 1, last updated on 2026-11-13. Download it on this page or copy its JSON, then import it into an n8n canvas. Nothing runs until you activate it in n8n.

## About

### What it is

This n8n workflow searches X for a phrase and turns the matching posts into one plain-text digest. You set the phrase and the number of posts in a settings node. The search itself runs on Xquik, a third-party service. A short code step numbers each post and adds its author and link. Five nodes make it up, and one of them is a note.

### Who it suits

Marketers, community managers and founders who want a quick read on what people say about a topic or a brand. Skip it if you need a lasting feed, since it runs when you press a button and stores nothing.

Who uses it, and how

| Industry | Who uses it | How they use it | Example |
| --- | --- | --- | --- |
| Marketing | Brand managers | Check mentions of a product name | A manager searches a product name and reads ten posts in one list. |
| Community | Community managers | Catch questions about a tool | A manager searches a tool’s name and spots a question nobody has answered. |
| Startups | Founders | Watch a launch phrase | A founder searches the launch hashtag the morning after a release. |
| Research | Analysts | Sample opinions on a topic | An analyst pulls a handful of posts on a topic before a deeper study. |

You need a little n8n: import a file, add a Header Auth credential and press a test button.

### Where to use it

Any n8n that can reach xquik.com will run it. It starts when you press the test button, and it needs no web form.

- n8n Cloud: import the file into a new workflow there
- Your own n8n server: the same file and steps
- Another search source: replace the \`Search X with Xquik\` request with any service that returns posts

### How to set it up

Download saves a zip with `workflow.json` and Mindket’s setup notes in your downloads folder. You need an Xquik account with credits and its API key.

What you need first

| Need | Detail |
| --- | --- |
| n8n | On n8n Cloud or on a server of your own |
| Xquik | An account with credits and an API key |
| A search phrase | Any phrase, hashtag or X search operator |

1. In n8n, create a workflow, open its menu, choose Import from File and pick `workflow.json`.
2. Create a Header Auth credential. Set its name to `x-api-key` and its value to your Xquik API key.
3. Select that credential in `Search X with Xquik`.
4. In `Search Settings`, type your phrase in `query` and set `limit`.
5. Press Execute Workflow and read the `digest` field in the output of `Build Digest`.

### How to use it

Change the phrase, run it again and read the digest. The output also carries `has_more` and `next_cursor`, which tell you whether more posts match.

What to change for a different result

| To change | Where |
| --- | --- |
| The phrase | \`query\` in \`Search Settings\` |
| How many posts | \`limit\` in \`Search Settings\` |
| The layout of the digest | The code in \`Build Digest\` |
| Where the digest goes | Add a mail or chat node after \`Build Digest\` |

### Example

A marketer sets `query` to `n8n automation` and `limit` to 10. Xquik returns up to ten matching posts. The digest lists them as numbered entries, each with its text, its author and a link, separated by blank lines. When nothing matches, the digest says that no posts were found.

### For newcomers and experts

**If you are new.** n8n draws a workflow as boxes joined by lines, and each box, a node, does one job. An HTTP Request node calls a web service and keeps its answer. A Header Auth credential stores a secret that n8n adds to each request.

**For experts.** `Search X with Xquik` sends `q` and `limit` as query parameters with a 120-second timeout, and `Build Digest` reads `tweets` from the answer. It accepts several field names for each value, so a small change in the service’s answer does not break it.

Where to look closer

| Node | What it does | What to know |
| --- | --- | --- |
| \`Search Settings\` | Holds the phrase and the post count | Edit them here, not in the request |
| \`Search X with Xquik\` | Calls Xquik’s tweet search | Costs 1 credit per post returned |
| \`Build Digest\` | Shapes each post and builds the text | Nothing is stored or sent |

### Good to know

Mindket’s copy reads the key from a credential, and the search service is a third party.

- Key: the file read the key from an \`XQUIK\_API\_KEY\` environment variable. The n8n 2.0 notes say environment access from the Code node is blocked by default, so Mindket’s copy uses a Header Auth credential
- Field names: Xquik’s page lists \`has\_next\_page\`, \`createdAt\` and \`likeCount\` where the file read \`has\_more\`, \`created\_at\` and \`metrics\`. The code now reads Xquik’s names first and keeps the old ones as a fallback
- Third party: Xquik says on its own pages that it is not affiliated with X Corp. Read its terms and X’s before you rely on it
- Cost: Xquik charges 1 credit for each post returned, so ten posts cost ten credits a run. When credits run out, it answers with a 402 error
- One page: the workflow reads one page of up to \`limit\` posts and does not follow \`next\_cursor\`
- No email: the digest is a text field, so add your own mail or chat node to send it
- Not run: Mindket read Xquik’s documentation and n8n’s source and did not call the service
- Your data: the search phrase goes to Xquik
- Credentials: the JSON holds none

## README

```markdown
# X search results turned into a text digest through Xquik

An n8n workflow that searches X for a phrase and turns the matching posts into one plain-text digest. You set the phrase and the number of posts in a settings node. The search runs on Xquik, a third-party service, and a short code step numbers each post and adds its author and link. Nothing is sent and nothing is stored.

## What is inside

- `workflow.json`: the workflow as n8n exports it, 5 nodes. Four run, and one is a sticky note that tells you how to add the key. It holds no credential.
- `README.md`: these notes.

## What we changed from the original copy

- `Search X with Xquik` sent its key in an `X-API-Key` header, read from an `XQUIK_API_KEY` environment variable. The n8n 2.0 breaking-changes page, read on 12 November 2026, says n8n now blocks environment variable access from the Code node by default. The request therefore uses a Header Auth credential, and the file holds no key.
- `Build Digest` read `has_more`, `created_at` and a `metrics` object. Xquik's documentation, read on 12 November 2026, lists `has_next_page`, `createdAt`, `likeCount`, `retweetCount` and `replyCount`. The code now reads Xquik's names first and keeps the old ones as a fallback.
- The sticky note is rewritten to say how to add the credential.
- Nothing else. The settings, the request and the digest layout are as the file had them.

Mindket read Xquik's documentation and n8n's source. It did not call Xquik and did not run this on a live n8n.

## Before you start

- An n8n instance, on n8n Cloud or your own server.
- An Xquik account with credits, and its API key.
- A search phrase. Xquik's page says the search takes X operators such as `from:`, `since:` and `until:`, hashtags, phrases and `OR`.

## Set it up

1. In n8n, create a workflow, open its menu and choose Import from File. Pick `workflow.json`.
2. Create a Header Auth credential. Set its name to `x-api-key` and its value to your Xquik API key.
3. Open `Search X with Xquik` and select that credential.
4. Open `Search Settings`, type your phrase in `query` and set `limit`.
5. Press Execute Workflow and read the `digest` field in the output of `Build Digest`.

## What happens in a run

1. `Manual Trigger` starts the run when you press Execute Workflow.
2. `Search Settings` sets two values: `query`, which is `n8n automation` in this copy, and `limit`, which is 10.
3. `Search X with Xquik` asks Xquik's tweet search for the matching posts, passing the two values as `q` and `limit` and sending your key through the credential. It waits up to 120 seconds.
4. `Build Digest` reads the `tweets` list and keeps each post's id, link, text, author, date and counts. When a post has no link, it builds one from the id. It writes `digest`, a numbered plain-text list, or a line saying nothing was found. It also returns the query, the number of posts, `has_more` and `next_cursor`.

## What to change

- The phrase: `query` in `Search Settings`.
- How many posts: `limit` in `Search Settings`.
- The layout of the digest: the code in `Build Digest`.
- Where the digest goes: add a mail or chat node after `Build Digest`.

## Good to know

- Xquik is a third-party service. Its own pages say it is not affiliated with X Corp. Read its terms and X's before you rely on it.
- Xquik charges 1 credit for each post returned, so ten posts cost ten credits a run. When credits run out, it answers with a 402 error.
- The workflow reads one page of up to `limit` posts. Xquik's page says to pass `next_cursor` back unchanged as `cursor` to get the next page, and this copy does not do that.
- The digest is a text field, so nothing is emailed. Add your own node to send it.
- Data: the search phrase goes to Xquik, and the posts that come back stay in n8n's run data.
```

## What is in it

3 files, 9 KB, downloaded as a zip.

```text
NOTICE.md  595 B
README.md  4 KB
workflow.json  4 KB
```

## Workflow check

Checked by Mindket on 13 Nov 2026. Read from the workflow’s file, not from a run.

- Steps: 4 steps, starting by hand
- AI: No step calls an AI model
- Sign-ins: Signs in to: xquik.com
- API keys: No API key is left in the file
- Step types: Mindket’s checker reads all 4 of its step types

## Get it

- [Get it on your Mindket account](https://account.mindket.com/account/?product=mindket#/market/8e08b56a-315d-400b-96c9-e61254d76f94)
- [Its page on Mindket](https://mindket.com/p/8e08b56a-315d-400b-96c9-e61254d76f94)