Resources · Make integration

Fomo Make integrationAutomate Fomo with Make.

Can Make push events into your Fomo feed on its own? Yes. The Fomo Make integration gives you 6 modules: 5 actions and 1 search. This page shows how to link your account, build a first scenario and pick the right module.

Try the Fomo integration on MakeSee the 6 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Fomo Make integration do for you?

The Fomo Make integration lets a Make scenario, meaning the automation you build in Make as a chain of modules, write to your Fomo account for you. It can add an event to your live Event feed, change it, look it up or remove it, using data that comes from your other apps.

A feed that fills itself. When a sale, a sign-up or a form reply lands in another app, Create an Event sends the details to your live Event feed. Nobody copies anything by hand, and the event carries the data mapped from the previous module.

Events that stay accurate. A customer fixes a typo in their name, or an order gets edited. List Events finds the matching event by external ID or email, then Update an Event changes the values that moved. If the order is cancelled, Delete an Event takes the event out of the feed.

Anything the list does not cover. Fomo has no trigger in Make, so a scenario always starts from another app or from a schedule. For endpoints that the five named modules skip, Make an API Call reuses the same connection to reach the rest of the Fomo API.

Many apps also exist on the n8n side; if you are weighing both tools, read n8n vs Make first. To check plans before you start, see Make pricing, and if you would rather learn the editor step by step, the Make training covers it.

Connect

How do you connect your Fomo account to Make?

  1. 01

    Copy your API token in Fomo

    In Fomo, select your website and open Settings. Go to the Site section and copy the API token shown near the bottom of the page. You need an active Fomo account for this to work.

  2. 02

    Add a Fomo module in Make

    In your scenario, add any Fomo module, for example Create an Event, and click Create a connection. A connection is your Fomo account linked to Make once, then reused by every Fomo module you add later.

  3. 03

    Name it and paste the token

    The Connection name field is optional, but a clear name helps when you run several websites. Paste the token you copied, or follow the on-screen instructions, and save. Make can now read and write your Fomo events.

First scenario

Build your first scenario with Fomo

GoalWhen a new order arrives in your shop app, Make creates a matching event in your Fomo live feed.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Since Fomo has no trigger, this first module comes from the app where your orders live.

  2. 02

    Pick the starting app

    Search your shop or form app by name, choose the module that returns new orders and click Create a connection for that app. Each order it finds becomes a bundle, one item passed to the next module.

  3. 03

    Add Create an Event

    Click the + on the right of the first module, search Fomo and choose Create an Event. Pick your Fomo connection, then map the customer and order data from the previous module into the event fields.

  4. 04

    Test with Run once

    Click Run once to execute the scenario a single time. Read the bundles each module received, then check your Fomo feed to see the new event.

  5. 05

    Schedule and switch it on

    Open the clock on the first module to set the schedule, every 15 minutes by default for a new scenario, then switch the scenario on. Each run of each module counts as one operation on your Make plan.

Modules

What each Fomo module does

Fomo gives you 6 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Fomo1

Create an Event

Action

In Make“Send notification parameters to your live Event feed.”

This module adds a fresh event to your live Event feed in Fomo, filled with the values you map from earlier modules, so a sale or sign-up recorded elsewhere shows up in Fomo without anyone typing it.

When to use it
right after the module that brings in a new order, booking or form reply from another app.
Watch out
each bundle creates one event, so test with Run once before you switch the scenario on.
Fomo2

Delete an Event

Action

In Make“Deletes a Fomo event by ID.”

Delete an Event removes one Fomo event by its ID, which keeps your feed free of entries that should no longer appear there, such as a refunded or cancelled purchase.

When to use it
when another app tells you an order was cancelled and you already know the Fomo event ID, often from List Events placed just before.
Watch out
a deleted event does not come back, so double check which ID you map.
Fomo3

Get an Event

Action

In Make“Fetch an event object by ID.”

Get an Event hands you the full content of one Fomo event when you already hold its ID, so the next modules can reuse its values without guessing.

When to use it
you stored the event ID somewhere, in a sheet or a CRM record, and want to read the event back before sending it to another app.
Watch out
it needs the Fomo ID itself; with only an email or your own reference, reach for List Events instead.
Fomo4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call gives you access to any endpoint of the Fomo API through the same connection, which covers the requests that the five named modules do not offer.

When to use it
you found an operation in the Fomo API documentation that has no dedicated module in Make.
Watch out
you write the request yourself, so keep the Fomo API reference open next to the editor while you set the path and the body.
Fomo5

Update an Event

Action

In Make“Change key-value pairs of an existing Fomo event.”

With Update an Event, an existing Fomo event gets new values for the key-value pairs you map, so a correction edits the entry already in the feed instead of adding a second one.

When to use it
a customer edits their name or an order changes after the event was created.
Watch out
the module works on one known event, so find it first with List Events, or with Get an Event if you already hold its ID.
Fomo6

List Events

Search

In Make“Fetch an event object by external ID or email address attribute.”

List Events finds Fomo events from an external ID or an email address, which is how you connect a record from your own tools to the matching event in Fomo.

When to use it
before an update or a deletion, when all you have is the customer email or your order reference.
Watch out
as a search, it can return zero, one or several bundles, and every following module then runs once for each of them.
Need help

Need help automating Fomo with Make?

A person reads every message.

FAQ

Fomo and Make: common questions

01Is the Fomo Make integration free?
Yes, on the Make side. Fomo is a standard app, so it works from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one per module run on one bundle. Your Fomo subscription is a separate matter, handled on the Fomo pricing page.
02What do you need to connect Fomo to Make?
You need an active Fomo account and its API token. In Fomo, select your website, open Settings, go to the Site section and copy the token shown near the bottom of the page. In Make, add a Fomo module, click Create a connection, give it a name if you like, and paste the token. That connection is then reused by every Fomo module in your scenarios, so you only set it up once per account.
03Does the Fomo Make integration have a real-time trigger?
No. Fomo has no trigger module in Make, neither scheduled nor instant. A Fomo scenario therefore starts elsewhere: on a trigger from another app, such as your shop or your form tool, or on the schedule you set on the first module, every 15 minutes by default. How fast an event reaches Fomo depends on that first module. If it is an instant trigger of the other app, the scenario runs as soon as that app calls Make; if it is scheduled, it runs at each interval.
04What if a Fomo module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Fomo API with the same connection, so an operation without a dedicated module is still within reach. You write the request yourself from the Fomo API reference, which asks a little more care than the ready-made modules. The Make documentation for Fomo also notes that its content was generated from the official Fomo documentation and may contain mistakes, so check important details with Fomo directly before you rely on them.
05Should you use Make or n8n for Fomo?
It depends on your setup. On Make, Fomo comes with 6 modules: create, update, get, list and delete events, plus Make an API Call for the rest of the API. If those cover your need and your other apps already run in Make, keeping everything in one place is simpler to maintain. If your automations live in n8n, check what the n8n side offers for Fomo before moving anything. Base the choice on the modules you actually need, not on the tool name.
Same platform

Other docs you might need on this stack.

Browse all integrations