Objectionly Zapier integrationAutomate Objectionly with Zapier.
The Objectionly Zapier integration gives you 0 triggers, 1 action and 0 searches. It does one job: feed every sales call recording or transcript into Objectionly for analysis, straight from the tool that records it. Here is how to set it up, what it costs and what trips it.
Verified Trustpilot reviews · AI, automation & growth agency
What the Objectionly Zapier integration does
Objectionly reads sales calls, flags the objections raised, scores each conversation and turns that into coaching material. Zapier's role is narrow: it takes a call from another tool, such as a recorder, a drive or a meeting app, and uploads it to Objectionly so nobody has to do it by hand.
One operation, Upload Call Transcript, and three outcomes that make it worth setting up:
Every call analysed, not just the ones reps remember. A recording dropped in a shared folder is uploaded on its own, with a title and a date. Calls filed under the right rep. The Zap passes the rep's email, phone or ID, and Objectionly attaches the call to that person, so scorecards stay per rep. Text-only calls count too. When there is no audio or video link, a plain transcript goes into the same field, which covers phone systems that only export text.
What Zapier cannot do here matters as much. Objectionly has no trigger on Zapier, so scores, tags and coaching insights never flow out to your CRM or chat through this integration. There is no search either, and no way to update or delete a call once sent. Your Zap must start in another app.
If you are weighing platforms for this kind of flow, the Make vs Zapier comparison sets out the criteria one by one.
Zapier vocabulary in one minute
Seven words come back on every Zapier screen. Plain definitions first, so the rest of the page reads cleanly.
- 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. Objectionly has none, so yours comes from another app, like a new file in a folder.
- Action
- What the Zap does once started: the step that writes, sends or moves something, here uploading a call to Objectionly.
- Task
- The unit Zapier bills: one action that completes successfully. Your plan counts these and nothing else.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer. An instant one is pushed by its app the moment the event happens.
- Filter
- A step that lets the Zap continue only when the incoming data meets your condition, and stops it otherwise.
- Connection
- Your Objectionly account linked to Zapier once, then reused by every Zap that uploads calls to it.
What it really costs to run
Objectionly is not a premium app, so it works on the free plan. Since it has no trigger, the speed of your Zap depends on the trigger of the app that starts it.
- Per call uploadedOne task
- Free plan100 tasks a month, unlimited Zaps
- Free plan Zap sizeTwo steps: one trigger, one action
- Premium appNo, available on the free plan
Each call uploaded successfully is one task. Watching the source app for new recordings costs nothing, however often Zapier checks, and an upload that fails is not counted. So the bill follows your call volume, one task per call. The trap: the free plan builds two-step Zaps only, one trigger and one action. A filter to skip files that are not calls, or a second action, makes the Zap multi-step and needs a paid plan.
Connect Objectionly to Zapier in three steps
- 01
Open the Apps page
In your Zapier account, open Apps and click + Add connection. You need an Objectionly account, plus read or write access to anything you do not own but want the Zap to write into.
- 02
Find Objectionly
Type Objectionly in the dialog's search box, pick it, then click Add connection. A new browser tab opens on the Objectionly side for the sign-in step.
- 03
Sign in and grant access
Log in to Objectionly in that tab and allow Zapier to use the account. The connection then appears in your list, ready for every Zap that uploads calls to it.
Your first Zap: upload each new recording
GoalEach new recording saved in a shared folder is checked by a filter, then uploaded to Objectionly for analysis.
- 01
Create the Zap and its trigger
Create a new Zap. Pick the drive where recordings land, with the event New File in Folder, and select the folder your recorder writes to.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent files of that folder, so you can map a real recording in the next steps. Drop one sample file in first if the folder is empty.
- 03
Add the filter (paid plans)
From the plus icon, add a Filter step so only call recordings go through. A filter makes this a multi-step Zap, which the free plan does not run.
- 04
Add Upload Call Transcript
Pick Objectionly and Upload Call Transcript. Map a title, the file from the trigger into the audio, video or transcript field, the rep's email, and the call date.
- 05
Test, then publish
Test the step and check the call appears in Objectionly under the right rep. When it does, click Publish to switch the Zap on.
The Objectionly action
Objectionly gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Upload Call Transcript
ActionIn Zapier“Upload a call transcript and metadata for processing.”
Sends one sales call to Objectionly for processing, with a short title, the recording or its transcript, the rep it belongs to and the date it happened. The call then shows up in the dashboards under that title.
When the Objectionly Zap breaks
Zapier attaches no help article and no documented error to Objectionly. What goes wrong comes from the fields this action requires and from general Zapier limits.
Four cases explain most failed or missing uploads. For a wider checklist, the Zapier troubleshooting guide covers the usual suspects, and the Zapier training goes deeper on multi-step Zaps.
The rep is not recognised
Objectionly matches the rep against emails, then saved identifiers. With a rep who is not set up, or a phone not saved as an identifier, Objectionly has no one to assign the call to.The recording link is private
The audio or video URL should be publicly reachable, or a Zapier file link. A private link may leave Objectionly nothing it can reach; fall back to a text transcript.Old calls are never uploaded
A Zap only reacts to what happens after it is switched on. Recordings already in the folder stay there, and moving that backlog is a separate job.A bulk drop is held back
Copy a huge batch of recordings into the watched folder at once, and Zapier's flood protection can hold the batch back instead of running it.
Need help automating Objectionly with Zapier?
A person reads every message.
