- Home
- Resources
- Integrations
- myPresences
myPresences Zapier integrationAutomate myPresences with Zapier.
myPresences Zapier integration: 1 action, 0 triggers and 0 searches. It is a narrow integration: another app starts the Zap, and myPresences creates a feedback request. It runs on the free plan, and the notes below say where it can trip.
Verified Trustpilot reviews · AI, automation & growth agency
What the myPresences Zapier integration actually does
It lets another app ask myPresences to create a feedback request, without anyone opening myPresences. Zapier runs automations called Zaps: each one waits for an event in one app, then does something in another. Here the event always comes from elsewhere, because myPresences offers one action and no trigger.
A feedback request after each form response. When your form tool records a new response, Add Feedback Request creates the matching request in myPresences. Nobody has to remember to ask. One trigger, one action: that fits the free plan.
A request for each new row. A row added to a spreadsheet can start the same action, so the request follows your own records instead of somebody's memory.
Requests only for the right cases. Put a filter between the trigger and the action, and only the responses or rows that meet your condition reach myPresences. A filter makes the Zap multi-step, so this version needs a paid plan.
What Zapier does not do here: it cannot react to anything that happens inside myPresences, since the integration has no trigger, and it cannot look up an existing request, since it has no search. It does not reach back to responses or rows created before the Zap was switched on either.
If you are new to the tool, see our Zapier review, and open our Make vs Zapier comparison if you are still choosing a platform.
Zapier vocabulary, in plain words
Seven words come back on this page. Here is what each one means when the last step is myPresences.
- Zap
- The automation you build: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event that starts the Zap, such as a new form response in another app. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does once it has started. With myPresences, that step creates a feedback request for you.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The count on your plan is a count of those.
- Polling vs instant trigger
- A polling trigger is checked on a timer; an instant one is reported by its app the moment the event happens, so nothing waits.
- Filter
- A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A filter or a second action makes one, and it then needs a paid plan.
What a myPresences Zap costs you
The trigger never costs a task, whichever app it comes from. What Zapier bills is the action: each feedback request that myPresences creates successfully counts once.
- Premium appNo, myPresences works on the free plan
- Free plan100 tasks a month, two-step Zaps only
- What countsEach request created successfully
- myPresences triggersNone, another app starts the Zap
An action that fails is not counted. If your Zap adds a second action after the request, each successful action counts on its own, and a few apps or actions take more than one task. The free plan gives you 100 tasks a month and unlimited Zaps, each limited to two steps: one trigger, one action. A filter or a second action makes the Zap multi-step, which needs a paid plan. Because myPresences has no trigger, the interval grid below applies to the trigger of the other app, and only when that trigger is a polling one.
Connect your myPresences account to Zapier
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. A connection is your myPresences account linked once, then reused by every step that talks to myPresences.
- 02
Pick myPresences
Type myPresences in the search box of the dialog, select it, then click Add connection. A new tab opens on the myPresences sign-in screen, where the rest of the setup happens.
- 03
Sign in and grant access
Log in to myPresences in that tab and allow Zapier to use the account. You need an account on the app, plus read or write access on anything you do not own yourself and want the Zap to touch.
Your first Zap: a feedback request for selected spreadsheet rows
GoalEach new row in your spreadsheet that meets your condition becomes a feedback request in myPresences.
- 01
Build the trigger
Create a Zap, pick your spreadsheet app and its new-row event, then select the exact sheet the Zap should watch for new rows.
- 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 row, not a placeholder.
- 03
Add the filter
From the plus icon, add Filter, then set the field to look at, the rule and the value. A filter makes the Zap multi-step, so this step needs a paid plan.
- 04
Add the myPresences action
Pick myPresences and Add Feedback Request, select your connection, enter the Business, then map the other fields the step offers from the row.
- 05
Test, then publish
Run each step once and read what came back. When the request shows up in myPresences as expected, click Publish to switch the Zap on.
myPresences actions in Zapier
myPresences gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Add Feedback Request
ActionIn Zapier“Create a feedback request”
Creates a feedback request in myPresences for one of the businesses under your account, using the data your trigger carried.
When a myPresences Zap breaks
Zapier lists no help article for myPresences, so the cases below come from how Zapier behaves with every app, plus the one mandatory field of the action.
Read these four cases before you publish. If a Zap still misbehaves, our Zapier troubleshooting page is the next stop.
Older rows get no request
A Zap only reacts to what happens after it is switched on. Rows or responses created earlier are not picked up; sending requests for them is a separate job.The Business field does not match
Add Feedback Request expects the name of a business under your connected account. If the value differs, check at test what comes back before publishing.A big import is held back
When the trigger of the other app suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold those runs back.The same row does not fire twice
On a polling trigger, Zapier keeps track of what it has already seen, so the same item does not start the Zap twice.
Need help automating myPresences with Zapier?
A person reads every message.



