# How to Automate Fansly Messages with n8n

> Learn how to automate Fansly messages with n8n using the OnlyFansAPI Fansly endpoints and webhooks. Streamline your workflow with direct messaging and auto-triggers.

**TL;DR**

- The `@onlyfansapi/n8n-nodes-onlyfansapi` community node covers the OnlyFans endpoints; the Fansly messaging endpoints take the same API key through an n8n HTTP Request node.
- On Basic and up, automated triggers like the `fansly.subscriptions.new` webhook event dispatch welcome messages and typing indicators without manual input.
- Fansly accounts use the same plans and per-account pricing as OnlyFans accounts, with their own `/api/fansly/` endpoints.
- On Basic and up, each connected account gets a dedicated mobile IP to keep every account protected, and OnlyFansAPI has zero bans in 5+ years.

To automate Fansly messages with n8n, create an OnlyFansAPI API key and call the Fansly endpoints from an n8n HTTP Request node with the header `Authorization: Bearer YOUR_API_KEY`. This setup allows you to trigger automated direct messages, welcome sequences, and scheduled mass PPV broadcasts across Fansly creator accounts using REST endpoints.

**Key Takeaways**

- The `@onlyfansapi/n8n-nodes-onlyfansapi` community node covers the OnlyFans endpoints; the Fansly messaging endpoints take the same API key through an n8n HTTP Request node.
- On Basic and up, automated triggers like the `fansly.subscriptions.new` webhook event dispatch welcome messages and typing indicators without manual input.
- Fansly accounts use the same plans and per-account pricing as OnlyFans accounts, with their own `/api/fansly/` endpoints.
- On Basic and up, each connected account gets a dedicated mobile IP to keep every account protected, and OnlyFansAPI has zero bans in 5+ years.

## How to Automate Fansly Messages with n8n

To automate Fansly messages with n8n, generate an API key in the developer console and send Fansly requests to `https://app.fansapi.com/api/fansly/{fanslyAccount}/...` from an HTTP Request node. Our official community node `@onlyfansapi/n8n-nodes-onlyfansapi`, installed from the n8n Nodes Panel, covers the OnlyFans endpoints with the same key. Agencies managing multiple creator profiles can remove manual messaging labor by routing these tasks through self-hosted or cloud-based [n8n workflows](https://fansapi.com/no-code).

The [OnlyFansAPI n8n Integration Guide](https://docs.fansapi.com/integrations/n8n) outlines the exact installation and authentication steps needed to connect your workspace.

### Step 1: Installing the n8n Community Node

Only the n8n instance owner can install verified community nodes. Once installed, all members of an n8n instance can use the node in their workflows.

Using the visual interface, log in to your n8n workspace and click "Create workflow" in the top right corner. Open the nodes panel, search for "OnlyFans API", select it, and click the "Install node" button next to the logo.

To update the node in self-hosted Docker environments, execute the following commands:

```bash
docker exec -it n8n sh
npm update @onlyfansapi/n8n-nodes-onlyfansapi
```

### Step 2: Generating API Keys and Credentials

Go to the OnlyFans API developer console, navigate to API Keys, and create a new API key. Give it a descriptive name for your production environment and click "Add". Copy this key to your clipboard.

Head to your n8n instance's homepage and click on "Create Credential" in the "Create Workflow" dropdown. Select "OnlyFans API" from the list of available credential types, click "Continue", paste the API key into the "API Key" field, and click "Save".

## Fansly Messaging Endpoints Reference

The API exposes dedicated REST routes for Fansly operations under `/api/fansly/{fanslyAccount}/`, on the same platform that runs at 99.98% uptime. All plans from Basic and up include one [dedicated mobile IP](https://fansapi.com/onlyfans-proxy) per connected account in the US or UK with no rotation. This infrastructure is built to keep every account protected.

| Endpoint Action | Method | API Path |
| --- | --- | --- |
| Send Chat Message | `POST` | `/api/fansly/{fanslyAccount}/chats/{chat_id}/messages` |
| List Chats | `GET` | `/api/fansly/{fanslyAccount}/chats` |
| Start Typing Indicator | `POST` | `/api/fansly/{fanslyAccount}/chats/{chat_id}/typing` |
| Acknowledge Messages | `POST` | `/api/fansly/{fanslyAccount}/chats/{chat_id}/messages/ack` |
| Send Mass Message | `POST` | `/api/fansly/{fanslyAccount}/mass-messaging` |
| Cancel Scheduled Mass Message | `DELETE` | `/api/fansly/{fanslyAccount}/mass-messaging/{broadcast_id}` |

## Practical Workflows for Fansly Chat Automation

Agencies build specific automation pipelines in n8n to handle high-volume interactions. You can create branching logic for different subscriber events to send the right direct message at the right time. Webhook triggers need Basic and up. For setting up daily operational and financial data extraction, refer to the [Automate OnlyFans with n8n and Baserow](/blog/onlyfans-api-automate-with-n8n-baserow) guide.

### Near Real-Time Welcome Messages

When a fan subscribes, the `fansly.subscriptions.new` webhook event triggers your workflow in near real-time. Take the fan's `subscriberId` from the payload, get the chat `id` with `POST /api/fansly/{fanslyAccount}/chats`, and dispatch a typing indicator using `POST /api/fansly/{fanslyAccount}/chats/{chat_id}/typing` to simulate human presence.

After a brief wait node, send the welcome text and vault media files using the [Docs: Send Chat Message](https://docs.fansapi.com/api-reference/fansly/chat-messages/send-chat-message) endpoint.

### High-Roller Tip Follow-Up

The `fansly.tips.received` webhook event detects incoming tips. Your n8n workflow can filter the payload amount, which Fansly sends in thousandths of a dollar (15000 = $15.00), to identify large transactions. When a tip exceeds a specific threshold, the workflow sends an internal agency alert and dispatches a personalized direct message containing a paid PPV media file.

### Scheduled Mass Messaging Campaigns

You can broadcast customized mass messages on a set calendar using the n8n schedule trigger. The workflow sends the broadcast to a `groupId`, the recipient filter set up on the Fansly dashboard, using the [Docs: Send Mass Message](https://docs.fansapi.com/api-reference/fansly/mass-messaging/send-mass-message) endpoint.

Example request body, with `price` in thousandths of a dollar (15000 = $15.00) and `scheduledFor` as a Unix timestamp in milliseconds:

```json
{
  "groupId": "200000000000000020",
  "text": "Weekend exclusive video just dropped! Check it out below.",
  "mediaFiles": ["fansly_media_01JR1234"],
  "requirePurchase": true,
  "price": 15000,
  "scheduledFor": 1785110911809
}
```

## Does OnlyFansAPI Charge Extra for Fansly Accounts?

Fansly accounts do not cost extra and are billed exactly like OnlyFans accounts, under the same plans and credits detailed on the official [Pricing](https://fansapi.com/pricing) page.

The Free tier supports 1 account, 60 RPM, and 100 one-time credits. The Basic plan costs $69/mo or $690/yr for 1 account, 1,000 RPM, and 20,000 credits/mo. The Pro plan costs $299/mo or $2,990/yr and includes 5 accounts, 5,000 RPM, and 100,000 credits/mo. Extra accounts on the Pro plan scale down from $29 to $11.60 per account.