Turn Every OFAPI Event Into a Multi-Step Workflow — No Code, No Developers
A subscriber expires. Make routes the event to your Google Sheet, fires a churn alert to Slack, and queues a re-engagement email — all from a single webhook trigger you built by dragging and dropping modules. No developer needed. No code written. Make's visual builder receives real-time OFAPI events and lets you route them through filters, routers, and 1,500+ app connections with branching logic you can see and edit at a glance. Connect in under 15 minutes.
Why Make over Other Automation Platforms
Visual scenario builder
See your entire workflow as a visual flowchart. Drag modules, draw connections, and add branching logic without any code.
Advanced routing and filters
Route events to different destinations based on amount thresholds, creator IDs, event types, or any field in the payload.
More operations per dollar
Make's pricing is based on operations, and their free tier includes 1,000 operations per month — enough for many small agencies.
Error handling built in
Add retry logic, error handlers, and fallback routes directly in the visual builder. No scripting needed.
Setup Guide
Create a Custom Webhook Trigger
In Make, create a new scenario and search for Webhooks in the module list. Select Custom webhook as your trigger. Click Add to create a new webhook and give it a name like "OFAPI Events". Make generates a unique URL.
https://hook.make.com/abc123def456ghi789 Register in OFAPI Dashboard
In the OFAPI dashboard, go to Settings → Webhooks and paste the Make URL as a new endpoint. Select the events you want (revenue.received, subscriber.new, etc.). Click Send Test Event so Make can learn the payload structure.
Add Modules and Activate
After Make receives the test payload, it auto-detects the data structure. Now add action modules — Google Sheets, Slack, Discord, HTTP, Gmail, or any of the 1,500+ supported apps. Use the Router module to send different event types to different destinations. Toggle the scenario to ON when ready.
Example Scenario: Revenue Router
This Make scenario receives all OFAPI events and routes them based on type:
# Trigger Module 1: Custom Webhook (OFAPI Events) # Router — splits by event type Module 2: Router # Route A — revenue events Filter: event = "revenue.received" Module 3: Google Sheets — Add Row Sheet: "Revenue Tracker" Row: [date, creator, amount, type] Module 4: Slack — Send Message Channel: "#revenue" Text: "${data.creator} earned $${data.amount}" # Route B — churn events Filter: event = "subscriber.expired" Module 5: Gmail — Send Email To: "manager@agency.com" Subject: "Churn alert: ${data.username}"
Every event your operation ignores today is a decision made without data
Revenue to Sheets. Churn to Slack. New subscribers to your CRM. Make routes each OFAPI event to the right destination automatically — no developer, no maintenance, no delays. Build your first scenario in under 15 minutes.