X search results turned into a text digest through Xquik

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.