Quickstart

Our Make.com integration is the easiest to use. Simply follow this guide to get started.

Prerequisites

To get started, you must have:

• An OnlyFans API account with a creator account connected
• A Make.com account

Getting started

1. Log in to your Make.com account.
2. Install our Make.com integration via this link: https://www.make.com/en/hq/app-invitation/ee8eed5fafe0c65c4989c5b7112b741d

Connecting your OnlyFans API account to Make.com

1. Go to a Make scenario, or create a new scenario

   Go to the Scenarios page in Make.com, click on the relevant scenario, or click on “Create a new scenario”.

2. Add the OnlyFans API app

   Click on the ”+” button to add an app, and search for “OnlyFans API”.

3. Select or search for a module

   

4. Add a new API connection

   

5. Create a new API key from the OnlyFans API Console
6. Save the new API key in Make.com

   Give the connection a helpful name, paste the API key, and click “Save”.

That’s it! You’re now ready to use the OnlyFans API app in your Make.com scenario.

Example scenarios with Airtable

To get started, we have created a few example scenarios that will show you around OnlyFans API’s Make integration.

Of course, you can also use any other app that Make.com supports, such as Google Sheets, Notion, etc.

The example scenarios use Airtable, so make sure you have an Airtable account before proceeding.

Tracking links + Airtable

For this example, we’ll create a scenario that periodically retrieves the tracking link data from all of your connected OnlyFans accounts, and saves the data to Airtable.

1. Create a base Airtable

   Go to Airtable and create a base. You can name it “OnlyFans API”, or anything else that will help you identify it later.

2. Create a table within your base

   Within the base, create a table named “Tracking links”. Give the table the following fields:

   • ID (primary) - Single line text
   • Campaign code - Single line text
   • Campaign URL - URL
   • Clicks count - Number
   • Subscriber count - Number
   • Total revenue - Currency

   Your table should now look like this:

3. Add our "List Accounts" module

   

4. Add our "List Tracking Links" module

   After adding “List Tracking Links” module, you will be asked to provide an “Account ID”. Simply click on the field, and drag the “ID” from the left card into the field, like in the below image. Make sure to click on “Save”.

5. Add the Airtable "Create a Record" module

   If you don’t see this module, make sure to click on “Show more”.

6. Connect your Airtable account, and select the correct Base and Table

   

7. Map the fields

   Now, let’s map the OnlyFans API module fields to your Airtable’s table fields. Make sure to click on “Save”. If you’ve done it correctly, your scenario should look like this:

8. Finally, schedule and run the scenario!

   You can set a schedule time, and then run it manually with the “Run once” button to see if everything works correctly.

   If it does, you will see the tracking link data of all your accounts appear in your Airtable table, like so:

That’s it! The tracking link data of all of your connected OnlyFans accounts will now automatically be updated in Airtable.

Of course, you can further customize this scenario for a more advanced setup.

Transaction data + Airtable

For this example, we’ll create a scenario that periodically retrieves the transaction data from all of your connected OnlyFans accounts, and saves the data to Airtable.

1. Create a base Airtable

   Go to Airtable and create a base. You can name it “OnlyFans API”, or anything else that will help you identify it later.

2. Create a table within your base

   Within the base, create a table named “Transaction data”. Give the table the following fields:

   • Transaction ID (primary) - Single line text
   • Account name - Single line text
   • Amount - Currency
   • Net amount - Currency

   Your table should now look like this:

3. Add our "List Accounts" module

   

4. Add our "List Transactions" module

   You will be asked to provide an “Account ID”. Simply click on the field, and drag the “ID” from the left card into the field. Afterwards, choose a start date like “-30 days”.

   Afterwards, make sure to click on “Save”.

5. Add the Airtable "Create a Record" module

   If you don’t see this module, make sure to click on “Show more”.

6. Connect your Airtable account, and select the correct Base and Table

   

7. Map the fields

   Now, let’s map the OnlyFans API module fields to your Airtable’s table fields. Make sure to click on “Save”. If you’ve done it correctly, your scenario should look like this:

8. Finally, schedule and run the scenario!

   You can set a schedule time, and then run it manually with the “Run once” button to see if everything works correctly.

   If it does, you will see the tracking link data of all your accounts appear in your Airtable table, like so:

That’s it! The transaction data of all of your connected OnlyFans accounts will now automatically be updated in Airtable.

Of course, you can further customize this scenario for a more advanced setup.

Ready-made scenarios

Account synchronization

This scenario will synchronize your OnlyFans accounts with Airtable, and update the data once a day.

Download scenario blueprint

Hourly account revenue data

This scenario will synchronize your OnlyFans account revenue data with Airtable. Every account will have one record for each day, which updates hourly.

Download scenario blueprint

How to use the scenario blueprints

We recommend creating a new scenario and importing the blueprint there.

If you import a blueprint while editing another scenario that hasn’t been saved, all the changes in that scenario will be lost.

To import a blueprint:

1. On the Scenario Builder toolbar, click the three dots > Import blueprint.

   

2. Click Choose File, select the blueprint file in .json format, and click Save.

   

The imported scenario appears in the Scenario Builder. You can now configure your own account connections, make any necessary edits to the scenario, schedule it, and click the Save icon.