OnlyFans + Power Automate
Power Automate has no OnlyFans connector, but it ships with a generic HTTP action that calls any REST endpoint. ofapis is Bearer-auth REST, so it slots straight into cloud flows — scheduled, triggered, or button-run — alongside the Microsoft 365 services your agency already uses (Excel, Teams, Outlook, Dataverse).
The action you need: HTTP + Authorization header
The plain HTTP action lives under Premium connectors. Add it and configure:
| Field | Value |
|---|---|
| Method | GET for reads, POST for sends |
| URI | https://api.ofapis.com/api/public/v1/accounts/42/subscribers |
| Headers | Authorization: Bearer ofapis_sk_... and Content-Type: application/json |
| Body | your JSON, for POSTs |
Don't paste the raw key. Store it in Azure Key Vault (or an environment variable / secure input) and reference it so the token never appears in the flow's run history. Follow the HTTP step with Parse JSON to turn the response into typed tokens you can use downstream.
POST https://api.ofapis.com/api/public/v1/accounts/42/mailings
Authorization: Bearer ofapis_sk_...
Content-Type: application/json
{ "text": "Weekend drop is live 🔥", "segmentId": "big-spenders" }
Worked example: nightly earnings into Teams
Trigger: Recurrence at 07:00 daily. Step 1 — HTTP GET /accounts/42/notifications?type=tips. Step 2 — Parse JSON and total the money events. Step 3 — Post message in a chat or channel dropping yesterday's total and top tippers into your ops channel. Because ofapis keeps the account session alive server-side, the recurring flow never stalls on re-authentication, and since only successful calls are billed, a transient upstream error simply fails the run at no credit cost — add a Retry policy on the HTTP action to smooth it over.
Three flows to build
- Recurrence → scheduled post. A weekly Recurrence trigger POSTs next week's scheduled post; build the caption from an Excel Online table row.
- When a new email arrives → auto-reply DM. An Outlook or Forms trigger (a fan request captured in your funnel) fires a POST to send a message.
- Request trigger → webhook fan-out. Use When an HTTP request is received as the target URL for an ofapis signed webhook; verify the signature, then branch on event type to Teams, Dataverse or a mass DM.
Every endpoint and its schema is in the OpenAPI docs, and the HTTP action calls all of them the same way.
FAQ
Is there a Power Automate connector for OnlyFans?
No. Use the built-in HTTP action (a Premium connector) with a Bearer token — it reaches every ofapis endpoint, so a custom connector is optional.
Do I need a Premium plan?
The generic HTTP action requires a Premium Power Automate license. Once you have it, no per-connector setup is needed; you point the action at the ofapis base URL.
How do I store the API key securely?
Reference it from Azure Key Vault or a secure environment variable rather than pasting it into the header field, so it stays out of flow run history. Rotate keys from the dashboard.
What happens when a flow run fails?
ofapis charges one credit only per successful call, so failed runs (expired session, 429) are free. Add a Retry policy on the HTTP action and check rate limits.
Where do I get a token?
Create one free — the Free plan's 250 monthly credits are enough to build and test a full flow before upgrading.
Related: Pipedream · Zapier · all integrations