Medallia Agent Connect Zapier integrationAutomate Medallia Agent Connect with Zapier.
The Medallia Agent Connect Zapier integration offers 0 triggers, 1 action and 0 searches. It does one job: it sends a customer a feedback request about a service interaction, started by an event in another app you already use.
Verified Trustpilot reviews · AI, automation & growth agency
What Medallia Agent Connect and Zapier do together
Medallia Agent Connect collects customer feedback on the agents who served them. With Zapier, an event in another app can ask for that feedback for you. The automation is called a Zap: one trigger (the event that starts it), then one or more actions (what it does next), every time the event happens.
On Zapier the app does a single thing, through Create Feedback Request, and the value comes from what you plug in front of it. Three results follow. A request after every logged interaction: a new row in your spreadsheet starts the Zap, and the action sends the request to the email in that row. Requests only for one service channel: a filter lets through only the rows whose channel matches, so the rest never reach the customer. No retyping between tools: the customer email and the channel are mapped from the earlier step, not copied by hand.
What Zapier does not do here: Medallia Agent Connect has no trigger, so nothing that happens inside it can start a Zap. A Zap always begins in another app. There is no search step either, so a Zap cannot look up a past request or a customer record in it. And the official description makes sending depend on other rules inside the app, so an action that runs is not proof that a request went out: check at test.
Comparing tools before you build? See our Make vs Zapier comparison or our Zapier review.
Zapier words you will meet on this page
Seven terms cover the rest of the page and the Zapier editor.
- 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. With this app it always comes from another tool, since Medallia Agent Connect has none.
- Action
- The step that does the work once the Zap has started, here sending a feedback request to a customer.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Your plan's allowance counts those.
- Polling or instant
- A polling trigger is checked by Zapier on a timer; an instant trigger is reported by the app the moment the event happens.
- Filter
- A step that lets the Zap go on only when what arrived meets your condition, and stops it there otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. Adding a filter or a second action makes one, and it needs a paid plan.
What a Medallia Agent Connect Zap really costs
The trigger never costs a task, and neither does Zapier checking for new data. Only an action that completes is billed.
- Free plan100 tasks a month, Zaps of two steps
- Premium appNo, works from the free plan
- BilledOne task per request sent
- Triggers in this app0, the Zap starts elsewhere
Each Create Feedback Request that succeeds counts as one task. An action that fails is not counted, and a few actions take more than one task. Medallia Agent Connect is not a premium app, so it works on the free plan: 100 tasks a month, unlimited Zaps of two steps each. A filter in front of the action makes the Zap multi-step, which needs a paid plan. The grid below is how often Zapier checks a polling trigger; it applies to the trigger of the other app if that trigger polls, never to this app, which has none.
Connect your Medallia Agent Connect account
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. You need a Medallia Agent Connect account, and access to anything you do not own that the Zap should touch.
- 02
Pick the app
Type Medallia Agent Connect in the search box of the dialog, select it in the results, then click Add connection. A new tab opens so you can sign in on the app's side.
- 03
Sign in and allow access
Sign in to Medallia Agent Connect in that tab and grant Zapier access to the account. The connection is saved once and reused by every Zap that sends feedback requests.
Your first Zap: a feedback request for one channel
GoalEach time a new row is added to your spreadsheet, send a feedback request to the customer email in that row, but only for the channel you choose.
- 01
Build the trigger
Create a Zap, pick your spreadsheet app as the one that starts it, and the event that fires on a new row. Connect the account and choose the sheet.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent items, so add a test row with a customer email and a channel first, then pick it.
- 03
Add the filter
From the plus icon, add Filter: the field to look at, the rule, the value to compare with. Use a text rule on the channel column. The Zap is now multi-step and needs a paid plan.
- 04
Add Create Feedback Request
Add Medallia Agent Connect and choose Create Feedback Request. Map Customer email from the row, then set Channel to a name that exists in your account.
- 05
Test, then publish
Test the action with your own email address and check what arrives. Then click Publish. Rows added before that moment are not picked up.
Medallia Agent Connect actions in Zapier
Medallia Agent Connect gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Feedback Request
ActionIn Zapier“Sends a feedback request (assuming other business logic passes).”
Asks a customer for feedback on the service interaction they just had, by sending the request to the email address you map.
When a Medallia Agent Connect Zap breaks
Zapier links no help article to this app and lists no limit of its own, so the cases below are general Zapier limits read against a send-only app.
Since every Zap here starts in another app, most of these cases sit on the trigger side. If a Zap stops behaving, see our Zapier troubleshooting guide.
No requests for past interactions
A Zap only reacts to what happens after you publish it. Interactions logged earlier are not picked up, and sending requests for them is a separate job.A flood of rows at once
If a bulk import suddenly adds many rows to the trigger app, Zapier's flood protection can hold the batch back instead of sending every request.A channel name that does not match
Channel must match a channel set up in Medallia Agent Connect. A value typed differently in the trigger app will not fit, so test with each channel you use.An action that runs but sends nothing
Per the official description, sending also depends on other rules inside the app. Check at test that the customer really receives the request.
Need help automating Medallia Agent Connect with Zapier?
A person reads every message.
