OnlyFans has no official public API, so every n8n automation for it needs a third party API layer, and CreatorAPI is built for exactly that role. It is one REST API with native OnlyFans and Fansly access behind a single key, and because it speaks plain HTTP with JSON, n8n can drive it with nothing more than the built in HTTP Request and Webhook nodes. This article walks through both directions: calling the API from a workflow, and receiving events into a workflow.
n8n fits because it is self hosted and HTTP native, which matches how an API like CreatorAPI wants to be used. You can run n8n on your own server, keep your API key in your own credential store, and wire any REST endpoint into a workflow without waiting for a vendor to ship a connector. The HTTP Request node covers every read and write CreatorAPI exposes, and the Webhook node gives you a public URL that CreatorAPI can push events to. For an agency that already runs its stack on its own infrastructure, that combination means full control with no extra middleman.
To call CreatorAPI from n8n, point an HTTP Request node at a native route and send your key in the X-API-Key header. Every native route follows one pattern: the method, then https://api.creator-api.com/v1/{account}/native/{path}, where {account} is the creator id you get when you connect an account. In the node, set the method and URL, then add a header parameter named X-API-Key with your ca_live_... key as the value. Store the key as an n8n credential rather than pasting it into the node directly.
Here is a concrete read, listing a creator's subscribers, exactly as the node will send it:
# GET request the HTTP Request node sends
GET https://api.creator-api.com/v1/{account}/native/subscriptions/subscribers?limit=50
X-API-Key: ca_live_your_key
The response is structured JSON, so downstream nodes can map fields without any parsing tricks. That stability comes from how the API works: it is not scraping, it calls the same authenticated endpoints the platform apps themselves use through your own connected session. Reads cost 1 credit and writes cost 2, so a scheduled workflow that polls a route every few minutes stays cheap and predictable. The quickstart covers connecting an account and making your first call in a few minutes.
To receive OnlyFans events in n8n, create a Webhook node, copy its production URL, and register that URL with CreatorAPI as a webhook endpoint. Registration is one call: POST /v1/{account}/webhooks with your n8n URL, and the event catalog at GET /v1/webhooks/events shows what you can subscribe to, including new messages, sales, renewals and new subscribers. From then on CreatorAPI pushes events to your workflow instead of you polling for them.
Deliveries are signed with HMAC SHA256, so you can verify inside the workflow that a payload really came from CreatorAPI before acting on it. Failed deliveries are retried with backoff, which matters for self hosted n8n instances that occasionally restart. You can also trigger a test delivery and inspect the delivery log while you build, so you never have to wait for a real sale to check your flow. The full event setup is documented on the OnlyFans webhooks page.
The two flows most teams build first are a subscriber CRM feed and a sales alert, and both need only three or four nodes. First, new subscriber to CRM sheet: a Webhook node receives the new subscriber event, a small function step picks out the fan's username and subscription details from the JSON payload, and a Google Sheets node appends a row. Your CRM sheet fills itself in real time, with no export ritual and no copy paste.
Second, sale posts to your team chat: a Webhook node receives the sale event, an IF node routes big purchases differently from small ones if you want that, and a Slack, Discord or Telegram node posts the amount and the fan to your team channel. Chatters see every sale the moment it lands, which is the kind of feedback loop that keeps a team sharp. From there the same pattern extends to renewals, expirations and message events.
There is no official CreatorAPI node for n8n yet, so the generic HTTP Request and Webhook nodes are the intended way to integrate, and they cover everything. We say that plainly because the generic nodes genuinely reach the full API surface: every native read and write, webhooks, exports, tags and smart links. The same approach works in Make and Zapier through their HTTP modules; the no code page shows the setup for each tool side by side. Start with the free trial of 1,000 credits, no card required, connect an account, and your first n8n workflow can be live the same afternoon.
Start free with 1,000 credits, no card required, and your first flow can be live today.