OnlyFans + Pipedream

Pipedream is a code-first workflow platform, which makes it a natural fit for ofapis. There is no prebuilt OnlyFans app, but you don't need one: every workflow can run a HTTP / Send any HTTP Request action or a full Node.js code step, both of which call ofapis's Bearer-auth REST endpoints directly — messaging, mass DMs, scheduled posts, subscribers, vault media and more.

The mechanism: HTTP action or Node.js step + connected key

Store the token once so it's encrypted and reusable. In your workflow, add an Environment Variable (OFAPIS_KEY) under Settings, then reference it from either step type.

The no-code way — add HTTP → Send any HTTP Request, set method + URL, and add a header Authorization: Bearer {{process.env.OFAPIS_KEY}}.

The code way — add a Node.js step:

export default defineComponent({
  async run({ steps }) {
    const res = await fetch(
      'https://api.ofapis.com/api/public/v1/accounts/42/subscribers?limit=100',
      { headers: { Authorization: `Bearer ${process.env.OFAPIS_KEY}` } }
    );
    if (!res.ok) throw new Error(`ofapis ${res.status}`);
    return (await res.json()).data;
  }
});

Whatever a step returns becomes steps.<name>.$return_value, so the next step can act on the fans you just pulled. Throwing on a non-2xx surfaces the error in Pipedream's inspector — and since ofapis bills only successful calls, that failed run costs nothing.

Worked example: incoming webhook → welcome DM

Start the workflow with an HTTP / Webhook trigger and register that URL as an ofapis signed webhook. On a message.received event — the event available today: step 1 verifies the signature in a code step, step 2 POSTs a reply to the fan's chat. Pipedream deploys the endpoint instantly and keeps every event in its inspector for replay, so debugging a live flow is just re-running a stored event. ofapis holds the session open server-side, so no refresh logic is needed.

Three workflows to build

• Schedule → nightly segment rebuild. A cron trigger pulls subscribers, buckets them in a code step, and POSTs refreshed fan segments.
• Webhook → tip thank-you. On a tip event, branch by amount and fire a message or a follow-up mass DM.
• Cron → scheduled post. Every Friday, read next week's caption from a data store and POST a scheduled post.

The OpenAPI spec lists every route; the same fetch pattern reaches all of them.

FAQ

Is there a prebuilt Pipedream app for OnlyFans?

No, and none is required. Pipedream's HTTP action and Node.js code steps both call every ofapis endpoint with a Bearer token, so you wire it in directly.

How do I connect my ofapis account securely?

Save the key as a workflow or project Environment Variable and reference process.env.OFAPIS_KEY in your steps, keeping it out of the code body and run logs. Rotate keys from the dashboard.

Can I trigger workflows from OnlyFans events?

Yes. Use an HTTP/Webhook trigger as the target for an ofapis signed webhook, verify the signature, then act on the event — Pipedream stores each event for replay while you build.

Do failed or retried runs cost credits?

No. Only successful calls are billed one credit each; expired-session and upstream errors are free, so retries stay cost-safe. See pricing and rate limits.

Where do I get a token?

Create one free — the Free plan's 250 monthly credits cover building and testing a full event workflow.

Related: Power Automate · n8n · all integrations