Resources · n8n integration

Apex n8n integrationAutomate Apex with n8n.

The Apex n8n integration moves posting, replying and tweet search out of the browser and into an n8n workflow. The node covers 6 operations spread across 5 resources, and the search operation alone accepts 24 optional filters. Nothing here listens on its own, so another node always starts the workflow.

Community node This node is not shipped with n8n: it is a community package (n8n-nodes-apex) you install from Settings › Community nodes on a self-hosted instance. npm

Try the Apex integration on n8nSee the 6 operations

Verified Trustpilot reviews · AI, automation & growth agency

Why automate

What does the Apex n8n integration actually do?

Apex handles social media accounts, and this node hands its tweet features to n8n. Six operations sit behind five resources: post a tweet, post a reply, read one tweet by ID, run a keyword search, and draft a reply either from a tweet ID or from raw text. Nothing here listens on its own, so every Apex workflow starts from another node, a Schedule Trigger on a fixed interval or a Webhook that a third party calls.

Take social listening first. A Schedule Trigger wakes the workflow, searchTweets.searchTweets pulls what matches your keywords, and each result lands in Google Sheets as a row your team can sort through later. Search is the richest operation of the six: its Additional Fields collection alone carries 24 entries, so you can narrow by hashtag, by author, by minimum likes or by date range without touching the API yourself.

Second scenario, assisted replies. Feed a tweet ID into generateReply.generateReplyToTweetId, let Apex draft an answer, then route the draft to a human. A Slack message with the text works well, or an If node that only forwards drafts above a certain length. Once someone approves, postReply.postReply publishes it against the same tweet ID.

Third, scheduled publishing. Rows in a spreadsheet, one column of copy, a Schedule Trigger every morning, and postTweet.postTweet sends the text to your profile. Pair it with an AI Agent upstream if the copy has to be generated rather than read from a list.

The node stops where Apex tweet features stop. There is no trigger, no timeline fetch beyond a single tweet by ID, and no account management operation. Anything the Apex API exposes and the node does not is still reachable through HTTP Request, reusing the same credential through predefined authentication. That is also the answer when a new Apex endpoint lands before the community package catches up.

One more thing worth knowing before you build: this node is not shipped with n8n. It comes from the npm package n8n-nodes-apex, which you install yourself on a self-hosted instance. On n8n Cloud, only verified community nodes are accepted, so check that before you plan a production workflow around it.

Connect

How do you connect Apex to n8n?

  1. 01

    Install the community package

    Open Settings, then Community nodes, and install the npm package n8n-nodes-apex (version 0.1.6). This step only exists on a self-hosted n8n, whether it runs from Docker or from npm. n8n Cloud accepts verified community nodes only, so if your instance is hosted by n8n and the package is not verified, the node will not appear in the panel. Once installed, Apex shows up in the node search like any built-in node.

  2. 02

    Create the Apex credential

    Go to the Credentials menu and add the Apex credential. A credential in n8n is a saved set of access details: you fill it once, and every workflow on the instance can reuse it, since the node offers it in its own dropdown list. Keep it on the account that owns the profile you plan to post from, because the tweets published by postTweet.postTweet land on that profile and nowhere else.

  3. 03

    Pick a starter and test one operation

    Apex has no trigger node, so drop a Schedule Trigger for a fixed interval, or an n8n Webhook, which is a URL another service calls to start the run. Wire it into the Apex node, choose Search Tweets, type one keyword and execute. If the result panel fills, the credential and the package are both fine. Testing with a read operation avoids publishing anything while you are still wiring things up.

Actions

The 6 Apex operations, one by one

The Apex node exposes 6 operations across 5 resources. For each one: the node as you configure it in n8n, the required fields, and our field notes.

Resources × operations matrix
ResourceGenerate Reply to TextGenerate Reply to TweetGet Tweet by IDPost ReplyTweetSearch Tweets
Generate Reply✓✓
Get Tweet✓
Post Reply✓
Post Tweet✓
Search Tweet✓

Generate Reply

2 operations
01

Generate reply to tweet id

generateReply.generateReplyToTweetId

What you see in n8n

Notes & use cases

Apex reads a tweet you point at and drafts an answer to it. Nothing is published: the draft comes back in the node output, ready for review or for a second node.

Key parameters

  • Tweet ID: the ID of the tweet to generate the reply for, usually passed as {{ $json.tweetId }} from a search result upstream.
Use cases
a mention lands in a search run, the draft goes to a reviewer, and only approved text moves on to the publishing step.
02

Generate reply to text string

generateReply.generateReplyToText

What you see in n8n

Notes & use cases

Same drafting, different input: here Apex works from a text string you supply rather than from something already posted. Useful when the source is not a tweet at all.

Key parameters

  • Text: the string Apex answers to, required, so an empty value stops the node.
Use cases
a support email body or a form answer flows in, and the node returns a short public reply your team can shorten before posting.

Get Tweet

1 operation
03

Get tweet by id

getTweet.getTweetById

What you see in n8n

Notes & use cases

Fetches one tweet from its ID, the number you find in the tweet URL. Read-only, and the natural first step when a workflow receives an ID but none of the content behind it.

Key parameters

  • Tweet ID: the ID of the tweet, found in the URL.
Use cases
a monitoring spreadsheet stores IDs only, and a nightly run reads each one back to refresh the stored copy.

Post Reply

1 operation
04

Post reply to tweet

postReply.postReply

What you see in n8n

Notes & use cases

Publishes a reply under an existing tweet. This one writes, so it belongs at the end of a branch where the text has already been checked.

Key parameters

  • Tweet ID: the tweet being answered, found in its URL.
  • Text: the reply body itself, required.
Use cases
the approval branch of a listening workflow ends here, posting the draft that a human validated a moment earlier.

Post Tweet

1 operation
05

Post tweet

postTweet.postTweet

What you see in n8n

Notes & use cases

Sends a standalone tweet to the profile behind the credential. No ID is involved, since nothing is being answered, which makes it the simplest operation of the six to wire up.

Key parameters

  • Text: the tweet content, required, so an empty column in the source data halts the run on that item.
Use cases
an editorial calendar kept in a sheet, one row per day, published by a Schedule Trigger that reads the row due today.

Search Tweet

1 operation
06

Search tweets

searchTweets.searchTweets

What you see in n8n

Notes & use cases

Runs a keyword search and returns matching tweets. Everything is optional here, which also means an unfiltered run brings back whatever is loudest.

Key parameters

  • Search Keyword(s): the words to look for.
  • Count: how many tweets to fetch; left empty, Apex returns 10.
  • Hashtags, Min Likes, Language: three of the 24 Additional Fields, for topic, engagement floor and ISO 639-1 locale.
Use cases
a weekly competitor watch, filtered on From Users and a date range through Start Date and End Date.
Need help

Need help automating Apex with n8n?

A person reads every message.

FAQ

Apex and n8n, the questions that come up

01Is the Apex n8n integration free?
On the n8n side, yes. Apex is a community node, which means it is not shipped with n8n and costs nothing to install: you add the npm package n8n-nodes-apex, version 0.1.6, from Settings then Community nodes on a self-hosted instance. n8n itself can be self-hosted through Docker or npm, or used on n8n Cloud, the hosting offer run by n8n, and a workflow behaves the same way on both. One caveat on Cloud: only verified community nodes are accepted there, so an unverified package will not install. What Apex charges for its own service is a separate question, and this page does not cover it.
02What credentials does the Apex node need?
One Apex credential, created in n8n. The node has no authentication selector, so there is nothing to choose between methods: you add the credential from the Credentials menu, fill it once, and it becomes available in the dropdown of every Apex node on the instance and in every workflow. That reuse is the point of credentials in n8n. Use the account tied to the profile you want to publish from, because Post tweet and Post reply write to whatever account the credential belongs to. The package has to be installed before the credential type appears.
03What are the limits of the Apex node in n8n?
Six operations across five resources, and that is the whole surface. You can post a tweet, post a reply, read one tweet by its ID, search tweets and generate a reply from either a tweet ID or a text string. There is no operation for anything else Apex may do with social media accounts. Search is the only operation with a filter collection, 24 Additional Fields covering dates, authors, engagement thresholds and a Cursor for the next batch of results. For anything missing, the HTTP Request node calls any endpoint of the API and reuses the same credential through predefined authentication.
04Can a workflow react to a new tweet in real time?
Not with this node, because Apex has no trigger node in n8n. A workflow that uses it starts somewhere else. Three options cover most needs. A Schedule Trigger runs the workflow on a fixed interval, which fits a search that sweeps keywords every hour or every morning. An n8n Webhook, a URL that a third-party service calls, starts the run the moment that service has something to say. Or the trigger of another tool in your setup kicks things off, and Apex simply becomes the step that posts or searches once the data is there.
05n8n or Make for Apex?
It depends on four things. Hosting: n8n runs on your own server through Docker or npm, while Make is hosted only, with no self-hosting option. Data control follows from that, since a self-hosted instance keeps tweet content and credentials on infrastructure you own. Cost model: Make bills per operation, so a search loop that runs all day is priced differently from one that runs twice. Visual logic differs too, and that is mostly a matter of habit. One practical point specific to Apex: this node is a community package, so it exists in the n8n world and not elsewhere.
Same platform

Other docs you might need on this stack.

Browse all integrations