Resources · Zapier integration

Olvy Zapier integrationAutomate Olvy with Zapier.

The Olvy Zapier integration gives you 13 triggers and 5 actions, and no search. Every trigger is instant, so a new piece of feedback, an issue or a release note reaches your other tools without waiting on a timer. It works on the free plan.

See the 18 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Olvy Zapier integration actually does

Olvy is where a product team collects user feedback, groups it into issues and tells users what shipped through release notes. Connecting it to Zapier lets each of those moments start an automation elsewhere, and lets other tools push contacts, feedback, issues or releases into Olvy.

Three results worth building. Feedback that lands in Olvy wherever it was given: a form, a survey or a support inbox feeds Create Feedback, so the product team reads everything in one place. A team told the moment a release goes out: Release Published starts a Zap that posts the news in your chat tool or your newsletter tool. Issues kept in step with your tracker: Issue Created and Issue Update copy each change of an Olvy issue to the tool your engineers work in.

Thirteen triggers, all instant, cover four objects: contacts, feedback, issues and releases, each with its create, update and archive events, plus a publish event for releases. On the action side, you can create each of those objects, and publish a release in one go.

What Zapier does not do here: there is no search, so a Zap cannot look up an existing contact or issue before writing; there is no action to update, archive or delete anything in Olvy; and nothing that happened before the Zap went live is picked up. If you are still picking a platform, see Make vs Zapier and n8n vs Zapier.

Vocabulary

Zapier words, in plain English

Seven words come back all over this page. Here is what each one means before you open the editor.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it to happen, here inside Olvy.
Action
What the Zap does after it starts: the step that creates, sends or publishes something for you.
Task
The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those.
Polling vs instant
A polling trigger is checked on a timer. An instant trigger is reported by the app itself the moment the event happens.
Filter
A step that lets the Zap carry on only when what arrived meets your condition, and stops it there otherwise.
Connection
Your Olvy account linked to Zapier once, then reused by every step of every Zap that touches Olvy.
Cost

What an Olvy Zap really costs

Zapier bills completed actions, not events. None of the 13 Olvy triggers ever costs a task, however much feedback comes in.

  • Any Olvy trigger0 task
  • Each successful action1 task
  • Free plan100 tasks a month, 2-step Zaps
  • Premium appNo

Each action that goes through counts as one task, and an action that fails is not counted. A Zap with three actions eats three times what a one-action Zap eats. Olvy is not a premium app, so it runs on the free plan: 100 tasks a month and unlimited Zaps, but only two steps per Zap. Add a filter, for example to keep only some feedback, or a second action, and the Zap becomes multi-step, which needs a paid plan. The polling grid below never applies to Olvy's triggers, since they are all instant.

Connect

Connect your Olvy account in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. You need an Olvy account first, plus access to anything you do not own yourself and want the Zap to touch.

  2. 02

    Pick Olvy

    Type Olvy in the search box of the dialog that appears, select it in the results, then click Add connection. A new browser tab opens on the Olvy side.

  3. 03

    Sign in and grant access

    Sign in to Olvy in that tab and allow Zapier to reach the account. The connection is saved once, then offered in every Zap step that uses Olvy from now on.

First Zap

Your first Olvy Zap: turn selected feedback into an issue

GoalWhen new feedback arrives in Olvy and meets your condition, an issue is created in Olvy so the product team can group and track it.

  1. 01

    Build the trigger

    Create a Zap, pick Olvy as the app and Feedback Created as the event, then select your Olvy connection, the one set up in the three connection steps above.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent items of the connected account, so you map the next steps on real feedback rather than an empty sample.

  3. 03

    Add the filter

    From the plus icon, add Filter. Pick the field to look at, the rule and the value. A text rule only works on text. This step makes the Zap multi-step.

  4. 04

    Add the action

    Add Olvy again with Create Issue. Map a short, readable value into the mandatory Name field so the issue makes sense in the list.

  5. 05

    Test and publish

    Test the action once and check the new issue in Olvy before going further, since it is a real one. Then click Publish to switch the Zap on.

Triggers

The 13 Olvy triggers

13 events start a Zap when something happens in Olvy, and 13 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Contact Deleted

Instant trigger

In Zapier“Triggers when a new contact is archived.”

Despite its name, this one starts your Zap when a contact is archived in Olvy. It is the signal to clean up the same person elsewhere, in a mailing list or a CRM.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a customer success team wants archived users removed from its onboarding sequence too.
Watch out
the label says deleted, the description says archived; test it on a real archive before relying on it.
2

Contact Created

Instant trigger

In Zapier“Triggers when a new contact is created.”

A new contact appears in Olvy, and the Zap runs with that person's details. Handy for keeping your contact lists in step without exporting anything by hand.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
every user who leaves feedback should also exist in your CRM, so sales can see who is asking for what.
Watch out
if another Zap creates contacts in Olvy, this trigger fires on those too.
3

Contact Updated

Instant trigger

In Zapier“Triggers when a contact is updated.”

Fires on an edit to an existing Olvy contact rather than on a new one. Use it to carry the change over to wherever else that contact lives.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a product manager corrects a company name in Olvy and the support desk should show the same thing.
Watch out
a Zap that writes back to the same contact would set this off again; keep the update one-way.
4

Feedback Archive

Instant trigger

In Zapier“Triggers when a feedback is archived”

When someone archives a piece of feedback in Olvy, the Zap kicks off. Archiving usually means the point is settled or out of scope, which is worth recording somewhere.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you log every closed request in a spreadsheet to review what the team chose not to build.
Watch out
nothing archived before the Zap was published will come through.
5

Feedback Created

Instant trigger

In Zapier“Triggers when a new feedback is created.”

The one Zapier puts forward for Olvy: each new piece of feedback starts the Zap. It is the natural entry point for routing what users say to the right person.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
new feedback should ping the product channel of your team chat so nobody has to refresh Olvy.
Watch out
never pair it with Create Feedback in the same Zap, or each new item creates another.
6

Feedback Updated

Instant trigger

In Zapier“Triggers when a certain feedback is updated.”

Reacts to a change on feedback that already exists in Olvy. Each edit runs the Zap again, so the copy kept in another tool stays current.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a support agent who forwarded a request wants to know when the product team edits it.
Watch out
several edits in a row mean several runs, and each action in them costs a task.
7

Issue Archived

Instant trigger

In Zapier“Triggers when an issue is archived”

Runs your Zap when an Olvy issue is moved to the archive. It closes the loop on issues mirrored in an engineering tracker or a roadmap board.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
an issue dropped in Olvy should be closed in the tracker your developers read every day.
Watch out
there is no Olvy action to archive, so the reverse direction cannot be automated here.
8

Issue Created

Instant trigger

In Zapier“Triggers when an issue is created”

Each new issue in Olvy hands its details to the Zap. Issues are where feedback gets grouped, so this is the moment a topic becomes real work.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
the engineering lead wants a matching ticket opened in the dev tracker for every new Olvy issue.
Watch out
issues created by your own Create Issue Zaps also start this one, so watch for chains.
9

Issue Update

Instant trigger

In Zapier“Triggers when an issue is updated”

Listens for edits on an existing Olvy issue. Good for keeping a status, a title or a description identical in two places without copying by hand.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a designer follows issues in a project board and needs each rename in Olvy reflected there.
Watch out
a busy issue can be edited often; add a filter if only some changes matter, on a paid plan.
10

Release Archived

Instant trigger

In Zapier“Triggers when a release is archived.”

Fires when a release in Olvy goes to the archive. Use it to take down or flag the same announcement wherever it was copied.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a marketing team mirrors release notes on a help center page and wants withdrawn ones marked as such.
Watch out
the Zap only learns about the archive; removing the copy elsewhere is the job of the action you add.
11

Release Created

Instant trigger

In Zapier“Triggers when a new release note is published.”

Starts the Zap on a new release in Olvy. Zapier's own description ties it to a release note being published, which overlaps with the next trigger.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a product marketer wants a draft announcement started in a doc each time a release is set up.
Watch out
test it against Release Published first, so you do not build two Zaps that fire on the same moment.
12

Release Published

Instant trigger

In Zapier“Triggers when a release note is published.”

Kicks in when a release note is published in Olvy, which is when users can read it. This is the trigger for spreading the word beyond Olvy.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
the support team should get the release note in its chat channel at the moment customers can read it.
Watch out
a release made by Create and Publish a Release also lands here.
13

Release Update

Instant trigger

In Zapier“Triggers when a release is updated.”

Picks up edits to a release that already exists in Olvy, such as a fixed typo or an extra paragraph. The copies elsewhere can follow.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
your changelog page outside Olvy must always match the text the team keeps polishing.
Watch out
small edits each start a run, so the task count can climb on a release that is reworked a lot.
Actions

The 5 Olvy actions

Olvy gives you 5 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Contact

Action

In Zapier“Creates a Contact”

Adds a person to Olvy from another tool, so their feedback can be tied to them later. Name is the only field the action insists on.

When to use it
a new customer signs up in your billing tool and should exist in Olvy before they ever write in.
Watch out
there is no search, so the action cannot check for an existing contact first.
2

Create Feedback

Action

In Zapier“Creates a Feedback”

Drops a new piece of feedback into Olvy, with its full text in the mandatory Body field. Zapier puts this action forward for the app.

When to use it
answers to an open question in your survey tool should be read by the product team in Olvy, not in a separate export.
Watch out
map the whole answer into Body, not just a subject line.
3

Create Issue

Action

In Zapier“Creates a New Olvy Issue”

Opens a new issue in Olvy, named after the value you map into the mandatory Name field. Issues are how feedback gets grouped by topic.

When to use it
a bug reported in your help desk should become an Olvy issue the product team can attach feedback to.
Watch out
combined with Issue Created in the same account, a careless chain can loop.
4

Create Release

Action

In Zapier“Creates a Draft Release”

Prepares a release in Olvy as a draft, with a Title and a body, both mandatory. Nothing is shown to users until someone publishes it in Olvy.

When to use it
a finished sprint in your project tool should leave a draft note the product manager polishes before release day.
Watch out
the draft stays unpublished; Zapier does not publish it afterwards.
5

Create and Publish a Release

Action

In Zapier“Creates and Publishes a Release Note”

Writes the release note and publishes it straight away, in one action. Title and body are both required, as with the draft version.

When to use it
small, routine updates that need no review, where speed matters more than wording.
Watch out
users see the text as mapped, typos included, and it also starts any Zap built on Release Published.
When it breaks

When an Olvy Zap breaks

Zapier links no help article to Olvy, so the cases below are the general ones that hit any Zap. With 13 triggers and actions that write into the same app, loops are the one to watch.

  • No catch-up on old feedback

    A Zap only reacts to what happens after it is switched on. Feedback, issues and releases already in Olvy stay where they are; moving that backlog is a separate job.

  • A Zap that feeds itself

    Feedback Created followed by Create Feedback, or Issue Created followed by Create Issue, sets the Zap off again and again and burns through the task count fast.

  • Flood protection after an import

    A bulk import of feedback or contacts makes the trigger return a huge batch at once, and Zapier's flood protection can hold it back instead of running it all.

  • A missing mandatory field

    Name, Body or Title left empty makes the action fail. A failed action costs no task, but the item never reaches Olvy, so check the mapping on a real record.
Need help

Need help automating Olvy with Zapier?

A person reads every message.

FAQ

Olvy Zapier integration: common questions

01Is the Olvy Zapier integration free?
Yes. Olvy is not a premium app, so it runs on the Zapier free plan. That plan gives you 100 tasks a month and unlimited Zaps, but each Zap is capped at two steps: one trigger and one action. A Zap from Feedback Created to Create Issue fits inside that limit. Add a filter, a second action or a step from another app, and the Zap becomes multi-step, which needs a paid plan. Plan your routing with that ceiling in mind.
02How many tasks does an Olvy Zap use?
One task per action that completes. None of the 13 Olvy triggers costs anything, however much feedback, how many issues or releases come through. A Zap with one action uses one task each time it runs successfully, and an action that fails is not counted. Busy triggers such as Feedback Updated or Issue Update can run often, and each run spends a task on its action, so on the free plan, with 100 tasks a month, choose them with care.
03Do Olvy triggers work in real time?
Yes. All 13 Olvy triggers are instant: Olvy tells Zapier the moment a contact, a piece of feedback, an issue or a release changes, so the Zap starts straight away. The polling interval of your plan, 15 minutes on the free plan, never applies to them. That makes Olvy a comfortable app to automate even without paying. In the editor, a Zap built on an instant trigger shows a lightning bolt, a quick way to confirm it.
04What does it take to connect an Olvy account to Zapier?
An Olvy account and a few clicks. Open the Apps page in Zapier, click + Add connection, search for Olvy, click Add connection, then sign in to Olvy in the tab that opens and grant access to the account. You also need access to anything you do not own yourself and want the Zap to touch. For actions, have the mandatory values ready: a Name for contacts and issues, a Body for feedback, a Title and body for releases.
05What is the difference between Release Created and Release Published?
The labels differ, but Zapier's own descriptions overlap: Release Created is described as firing when a new release note is published, and Release Published when a release note is published. Test both on a real release before building, and keep only the one that matches the moment you care about. On the action side, Create Release leaves a draft, while Create and Publish a Release puts the note live at once, and that also starts Release Published.
06What if the Olvy operation you want is not available?
Then Zapier cannot do it for now. The integration has 13 triggers and 5 actions, and no search, so a Zap cannot look up an existing contact or issue, nor update, archive or delete anything in Olvy. Those jobs stay inside Olvy itself. Another automation platform may expose a different set of Olvy operations, so compare what each one actually offers before you commit, rather than hitting the gap halfway through a workflow.
07Zapier, Make or n8n for Olvy?
Decide on criteria rather than on a ranking. On Zapier, Olvy offers 13 instant triggers and 5 actions, and it is not premium, so a two-step Zap runs on the free plan. For any other platform, check three things: whether it exposes the Olvy events and actions your scenario needs, how it bills each run, and whether its free tier allows the number of steps you plan to chain. The answer depends on your scenario, not on the tool.
Same platform

Other docs you might need on this stack.

Browse all integrations