- Home
- Resources
- Integrations
- Orbit by Marmeto
Orbit by Marmeto Zapier integrationAutomate Orbit by Marmeto with Zapier.
The Orbit by Marmeto Zapier integration offers 2 triggers, 0 actions and 0 searches. Both triggers are checked by Zapier on a timer, so your plan decides how fast an event from your partner program reaches your other tools. Here is what that means in practice.
Verified Trustpilot reviews · AI, automation & growth agency
What the Orbit by Marmeto Zapier integration does
The Orbit by Marmeto Zapier integration takes events from your partner platform and hands them to your other tools. On Zapier you build a Zap, an automation that starts with one event and then runs one or more steps. With Orbit by Marmeto, the start is always one of two triggers, and everything after it happens in other apps.
Three outcomes make sense here. A partner lead log: each event picked up by the first trigger becomes a row in a spreadsheet, so the team has one list to sort and share. A sales handoff: the same event creates a contact in your CRM, so a referred lead does not wait for someone to copy it. A team heads-up: a message lands in a shared channel or an inbox, so the partner manager sees new activity without logging in.
Now what this integration does not do. Zapier cannot write anything back into Orbit by Marmeto: no action creates a partner, records a commission or updates a lead, and no search looks one up. Data travels one way, out, so any change on the partner side is made in the platform itself. Both triggers are also polling triggers, which means a delay you cannot remove on the free plan, and nothing that happened before the Zap went live is picked up.
To get the basics of building Zaps in a structured way, there is a Zapier training page.
Zapier vocabulary in one minute
Seven words do the heavy lifting on this page. Here they are in plain English.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run each time that trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for it and does nothing before.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something for you, here in another app.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Your plan's quota is a count of those.
- Polling trigger
- A trigger Zapier checks on a timer: it asks the app for new items at a fixed interval and keeps only what it has not seen.
- Filter
- A step that lets the Zap continue only when what arrived meets your condition, and stops it quietly otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A filter or a second action makes it one, and it then needs a paid plan.
What Orbit by Marmeto costs you on Zapier
Orbit by Marmeto is not restricted to paid plans: it runs on the free plan. Its triggers never cost a task, and Zapier checking for new items costs nothing either, however often it looks.
- Free plan100 tasks per month, unlimited Zaps
- Free plan Zap size2 steps: one trigger, one action
- Orbit by Marmeto triggers0 instant, 2 polling
- Paid-only appNo
You pay for actions in the next apps. Each action that succeeds in those apps counts once, and a failed action is not billed. Two actions per event means two tasks per event. The free plan builds two-step Zaps only: add a filter or a second action and the Zap needs a paid plan. Since both triggers poll, the grid below is the one that matters here: it sets how long an event can wait before your Zap sees it.
Connect Orbit by Marmeto to Zapier
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. A connection is your Orbit by Marmeto account linked once, then reused by every Zap that starts from it.
- 02
Select Orbit by Marmeto
Type Orbit by Marmeto in the dialog, pick it, then click Add connection. You need an account on the platform, plus access to anything you do not own that the Zap should read.
- 03
Sign in and grant access
Sign in to Orbit by Marmeto in the tab that opens and allow Zapier to reach the account. From then on, the connection shows up in the list on both triggers.
Your first Orbit by Marmeto Zap, step by step
GoalSelected events from your partner program become rows in the spreadsheet your partner manager follows.
- 01
Build: pick the trigger
Create a Zap, choose Orbit by Marmeto as the app and Webhook as the event, the one that carries partner activity. Then select the connection you added earlier.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent items of the connected account, so the mapping is done on a real event rather than on blanks.
- 03
Add a filter
Click the plus icon, choose Filter, then set the field to read, the rule and the value. Use a text rule on text and a number rule on numbers, or nothing ever passes.
- 04
Add the spreadsheet action
Add your spreadsheet app as the action and map each value from the event into its column. Test the step once and open the sheet to check the row.
- 05
Publish
Click Publish. With the filter, the Zap has three steps and needs a paid plan, which also shortens the wait between checks to 2 minutes or less.
Orbit by Marmeto triggers on Zapier
2 events start a Zap when something happens in Orbit by Marmeto. Zapier checks for them at the interval your plan allows.
Webhook
Polling triggerIn Zapier“Triggers when the webhook url respective to the event fires.”
Picks up a new event that Orbit by Marmeto has recorded for the event type it is tied to, and passes it to the next steps. It is the trigger to start from when partner activity, such as a referred lead, should travel into your sales tools.
New Webhook
Polling triggerIn Zapier“Triggers when a new webhook is created for an event.”
Starts your Zap when a new notification link is created for one of the events in Orbit by Marmeto. In other words, it follows the setup of your account rather than partner activity itself.
When your Orbit by Marmeto Zap breaks
Zapier lists no help article and no rate limit specific to Orbit by Marmeto. What goes wrong comes from how Zapier handles polling triggers in general.
Four cases cover most surprises. If none of them matches yours, the Zapier troubleshooting page is the next stop.
The Zap seems slow
Both triggers poll. On the free plan Zapier checks every 15 minutes, 2 on Professional and 1 on Team or Enterprise. The delay is the plan, not a fault.Old events never show up
A Zap only reacts to what happens after it is switched on. Events already stored in Orbit by Marmeto are not picked up; moving that backlog is a separate job.A big batch is held back
When a trigger suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold it back instead of running every item.An event does not run twice
Zapier keeps track of what it has already seen on a polling trigger. The same item never starts the Zap twice: that is by design, not a missed event.
Need help automating Orbit by Marmeto with Zapier?
A person reads every message.



