INTEGRATIONS

Integrations

TwitterAPIs is a plain REST API, which means it drops into any automation platform that can make an HTTP request with a custom header. There is no connector to install and no app to authorise, because all 51 endpoints are ordinary GET and POST calls with one header. Below is the exact step to pick and the exact field to fill on each of the four platforms people ask about most, including where one of them is more work than it looks.

Platform	What to add	Header field	Where the key lives	Effort
n8n	HTTP Request node	Send Headers	Generic Credential Type, then Header auth or Bearer auth	One node, no code
Make	HTTP app	Headers	A connection with Authentication type set to API key	One module, no code
Zapier	Webhooks by Zapier, action Custom Request	Headers	Entered as a header value on the step	One step, no code
Composio	Custom MCP, or a custom tool written in the SDK	Not applicable, this path is code	API key or OAuth on the toolkit you register	Developer work, not a no-code step

The request every platform is making

Whatever the interface calls its fields, this is the call underneath. Get this working in a terminal first, then reproduce the same four parts in the platform: method, URL, query parameter, header.

GET https://api.twitterapis.com/twitter/user/info?username=naval
Authorization: Bearer YOUR_API_KEY

# or, if the platform prefers a named key header
x-api-key: YOUR_API_KEY

Platform by platform

n8n

n8n HTTP Request docs

Add the HTTP Request node. Custom headers go in Send Headers.

Bearer auth in n8n is header auth with the name preset to Authorization and the value preset to Bearer plus your token, which is exactly the shape this API expects.
Header auth takes a name and a value directly, so it also covers the x-api-key form if you prefer that header.
Storing the key as a credential rather than typing it into the node keeps it out of the workflow definition you export or share.

Make

Make HTTP app docs

Add the HTTP app. Custom headers go in Headers.

The module carries separate fields for URL, Method, Headers and Query parameters, so a read call is four fields and no code.
Make's own documentation says you do not need the Headers field for credentials, because the authentication type has its own field for that.
Older Make help pages split this app into several named sub-actions. If the screen in front of you does not match, look for the HTTP app rather than a specific action name.

Zapier

Zapier Webhooks docs

Add the Webhooks by Zapier, action Custom Request. Custom headers go in Headers.

Custom Request supports GET, PUT and POST, which covers every read endpoint on this API.
Zapier's documentation is explicit that credentials typed into step fields are stored in plain text and readable by anybody with access to the Zap, so treat a key used this way as shared with everyone on that account.
A newer app called API by Zapier adds a reusable connection with an authentication type named Static Headers, which fits an API key properly. It is labelled a beta feature in Zapier's own docs, and those docs give contradictory answers about which plans include it, so check inside your own account before planning around it.

Composio

Composio Custom MCP docs

Add the Custom MCP, or a custom tool written in the SDK. Custom headers go in Not applicable, this path is code.

Composio is an agent tooling layer rather than a visual workflow builder, and it has no generic HTTP action with a headers field the way the other three do.
Its Custom MCP path expects you to host an MCP server at a public address and register it, and Composio's documentation marks that path experimental and available through its API rather than its dashboard or SDK.
Its proxy execute helper rejects cross-domain requests by design, so it cannot be pointed at an API that is not already a registered toolkit.

For agents rather than workflows

A workflow platform is the right tool when the steps are fixed and the schedule is known. When the consumer is an AI assistant deciding what to fetch as it goes, the MCP server is the better fit: it exposes 51 tools an assistant calls by name, so there is no URL to build and no header to remember. n8n, Make and Zapier each now ship a client that can connect to a remote MCP server as well, and each of those vendors labels its own client a beta feature at the time of writing, so treat that route as promising rather than settled.

If you would rather write the integration yourself, the language clients page carries a working client for six languages, the quickstart gets a first response back in about a minute, and the REST API reference covers paging and the error contract your retry step will branch on.

Frequently Asked Questions

No. There is no listed connector in any marketplace, and this page does not pretend otherwise. What there is instead is a plain REST API that every one of those platforms can call through its own generic HTTP step, which is a documented, supported path rather than a workaround. The practical difference is that you set the URL and one header yourself instead of picking a logo from a list.

Webhooks by Zapier, which carries the Custom Request action, is listed by Zapier as available on its Free plan as well as the paid ones. Note that Zapier's own documentation warns that credentials typed into step fields are stored in plain text and are readable by anybody with access to the Zap, which is a real consideration for a shared account. Zapier's newer API by Zapier app stores keys as a proper connection, but its docs give conflicting answers on plan availability, so confirm that one in your account.

If the consumer is an AI agent rather than a workflow, yes. The MCP server exposes 51 tools an assistant can call by name, with no URL building and no header handling, and n8n, Make and Zapier all now ship a client that can connect to a remote MCP server. Both of those clients are labelled beta by their own vendors at the time of writing. For a deterministic workflow that runs on a schedule, a plain HTTP step is simpler and easier to debug.

Add an HTTP Request node, set the method to GET and the URL to the endpoint you want. Turn on Send Headers and add the Authorization header, or better, create a Generic Credential of type Bearer auth and paste the key there so it is stored as a credential rather than sitting in the workflow. The response arrives as JSON that the next node can read directly.

n8n and Make are the closest to one step: both have a first-class headers field and a reusable credential built for an API key, so the key never has to be pasted into the step itself. Zapier is equally quick to get working but asks more care about where the key ends up. Composio is a different category, since it has no generic HTTP action and expects either a hosted MCP server or code.

The API side is per call at $0.0008 for a standard read, with no plan minimum and no seat count, so a workflow that runs hourly costs the number of calls it makes. The thing to watch is a loop: a scenario that pages through a large follower list makes one billed call per page, and a retry step that repeats a failed call bills for each attempt.

Free tools Start Free