Resources · Zapier integration

ONES Zapier integrationAutomate ONES with Zapier.

ONES Zapier integration: 3 triggers and 2 actions. All three triggers are instant, so a new issue, an edited issue or a fresh comment in ONES starts your Zap straight away, and the actions open issues or add comments from your other tools.

See the 5 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the ONES Zapier integration does for a product team

The ONES Zapier integration links the issues your team tracks in ONES to the other tools it works in, with Zapier passing things along. Zapier runs small automations called Zaps. With ONES, a Zap can start from an issue or a comment, and it can open an issue or comment on one for you.

Bug reports that land as issues. A support ticket flagged as a bug, or a form filled in by a tester, becomes a ONES issue through Create Issue, without anyone retyping it.

A team that hears about new work right away. New Issue starts a Zap the moment an issue is created in ONES, so the team channel or the on-call person gets it with no wait.

Discussions kept on the issue. A decision taken in another tool goes back on the issue through Add Comment to Issue, and New Comment can relay what people write in ONES to wherever the rest of the team reads.

What Zapier does not do here matters as much. There is no search step for ONES, so a Zap cannot look up an existing issue on its own. No action edits or closes an issue, and none deletes anything. A Zap also ignores every issue and comment created before you switched it on.

Comparing tools for the same job? See Make vs Zapier and n8n vs Zapier.

Vocabulary

Zapier vocabulary in one minute

Seven words come back all over this page. Here they are in plain English, once.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it, here a new issue, an issue update or a new comment.
Action
What the Zap does once started: the step that writes, sends or moves something for you, such as opening an issue in ONES.
Task
The unit Zapier bills. One task is one action your Zap completes successfully, and your plan gives you a set number of them.
Instant trigger
A trigger the app reports itself, the moment the event happens, so nothing waits for a check. All three ONES triggers work this way.
Polling trigger
A trigger Zapier checks on a timer, asking the app for new items at a fixed interval. ONES has none, which spares you the wait.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it there otherwise.
Cost

What a ONES Zap really costs

ONES is not reserved for paid plans: it works on Zapier's free plan. What you spend is tasks, and nothing else is billed.

  • TriggerNo task
  • Successful action1 task each
  • Failed actionNot counted
  • Free plan100 tasks a month, two-step Zaps
  • ONES triggersInstant on every plan

The trigger costs nothing, however many issues ONES reports. Each action that goes through counts once, and one that fails is not counted. In a Zap with three actions, every success counts on its own, so it eats three times what a one-action Zap does. The free plan gives 100 tasks a month and stops at two steps, one trigger and one action. Add a filter or a second action and the Zap becomes multi-step, which needs a paid plan. The interval grid below does not apply to ONES: its triggers are instant on every plan.

Connect

Connect ONES to Zapier in 3 steps

  1. 01

    Open the Apps page

    In your Zapier account, open Apps and click + Add connection. A connection is your ONES account linked to Zapier once, then reused by every step that touches ONES.

  2. 02

    Pick ONES in the dialog

    Type ONES in the search box of the dialog, select it from the results, then click Add connection. A new tab opens on the ONES side so you can sign in.

  3. 03

    Sign in and grant access

    Sign in to ONES in that tab and grant Zapier access to the account. Any project you do not own but want a Zap to read or write into needs read or write access for your account first.

First Zap

Build your first ONES Zap

GoalWhen a new issue is created in ONES, add a comment to it, but only for the issues that pass a filter.

  1. 01

    Pick the trigger

    Start a new Zap, choose ONES as the app that starts it and New Issue as the event, then select the ONES connection you made earlier.

  2. 02

    Test it on real data

    Run the trigger test. Zapier brings back the three most recent items of your connected account, so the rest of the Zap is set up on a real issue, not an empty sample.

  3. 03

    Add the filter

    Add a Filter step from the plus icon and fill its three boxes: the field to look at, the rule, the value to compare with. A text rule only works on text.

  4. 04

    Add the comment

    Add ONES again, this time with Add Comment to Issue as the action, and map the issue that the trigger brought in so the comment lands on the right one.

  5. 05

    Test, then publish

    Test the action and read what came back before going further. When the comment looks right, click Publish to switch the Zap on. With its filter, it needs a paid plan.

Triggers

ONES triggers on Zapier

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

1

New Comment

Instant trigger

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

New Comment starts your Zap each time someone writes a new comment in ONES, and hands that comment to the following steps so they can pass it on or act on it.

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 wants comments left by engineers on customer-facing issues relayed to the account manager who owns that customer.
Watch out
a Zap started by New Comment that runs Add Comment to Issue writes a comment itself, which can start the same Zap again and burn tasks.
2

New Issue

Instant trigger

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

This trigger fires when a new issue is created in ONES. The issue travels to the next steps, which can announce it, copy it into a planning sheet or comment on it.

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 QA lead wants every new issue posted in the release channel, so nobody discovers a blocking bug the day before shipping.
Watch out
a Zap that runs Create Issue in the project New Issue watches creates an issue, then starts again on it, in a loop.
3

Update Issue

Instant trigger

In Zapier“Triggers when an issue is updated.”

Update Issue watches existing issues and starts the Zap when one of them is updated. Use it when what matters is the life of an issue after creation, not its birth.

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 lead wants to know when an issue linked to a customer ticket moves, so the customer hears about it from support first.
Watch out
every update starts the Zap, including minor ones; a filter keeps only the changes worth a task.
Actions

ONES actions on Zapier

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

1

Create Issue

Action

In Zapier“Create a new issue.”

Create Issue opens a new issue in ONES from what an earlier step brings in, so a report written in another tool reaches the backlog without copy and paste.

When to use it
a bug reported through your help desk should become an issue the engineering team can triage the same day.
Watch out
each issue created is one task, so a noisy source feeding this action eats into the 100 free tasks a month.
2

Add Comment to Issue

Action

In Zapier“Add a new comment to an issue.”

This action adds a new comment to an existing ONES issue. Whatever earlier steps gathered ends up in the discussion people already read.

When to use it
a customer reply arriving by email should appear as a comment on the issue it concerns, so engineers see it without switching tools.
Watch out
the Zap has to know which issue to comment on, and with no search step for ONES, that issue must come from an earlier step.
When it breaks

When a ONES Zap breaks

Zapier attaches no help article to ONES and lists no limit of its own for it. What breaks is what breaks on any Zap, and one case bites harder here, because the actions write exactly the kind of thing the triggers watch.

Read the four cases below before you switch the Zap on. If one catches you anyway, there is the Zapier troubleshooting page.

  • Nothing from before the Zap

    A Zap only reacts to what happens after you switch it on. Issues and comments created in ONES before that are never picked up, and moving that backlog is a separate job.

  • A Zap that sets itself off

    New Issue with Create Issue, or New Comment with Add Comment to Issue, in the same place: the Zap writes where it watches, starts again and burns tasks.

  • A sudden flood of issues

    After a bulk import or a migration into ONES, a trigger that suddenly returns a huge batch can be held back by Zapier's flood protection.

  • An update storm

    Update Issue starts the Zap on every update. A busy issue edited many times in a row runs the Zap as many times, and each successful action is a task.
Need help

Need help automating ONES with Zapier?

A person reads every message.

FAQ

ONES and Zapier: common questions

01Is the ONES Zapier integration free?
Yes, as long as the Zap stays at two steps. ONES is not reserved for paid plans, so it runs on Zapier's free plan, which gives 100 tasks a month and an unlimited number of Zaps. The limit is the shape of the Zap: one trigger and one action, nothing more. Add a filter or a second action, and the Zap becomes multi-step, which needs a paid plan. The good news on the free plan is speed: the three ONES triggers are instant, so you do not wait for a check.
02How many tasks does a ONES Zap use?
One per action that succeeds. The trigger costs nothing, however many issues or comments ONES reports. Each ONES action that goes through, Create Issue or Add Comment to Issue, counts as one task, and an action that fails is not counted. In a Zap with three actions, each success counts on its own, so it uses three times what a one-action Zap does. Watch Update Issue in particular: it starts the Zap on every update, and a few apps and actions take more than one task.
03Does ONES work in real time with Zapier?
Yes. New Comment, New Issue and Update Issue are all instant triggers: ONES itself tells Zapier when the event happens, so the Zap starts right away. The interval grid of the plans, 15 minutes on Free down to 1 minute on Team and Enterprise, only concerns polling triggers and does not apply here, whatever your plan. In the editor, a Zap built on one of these triggers shows a lightning bolt. That type is decided on the ONES side and cannot be changed from the editor.
04What does connecting ONES to Zapier require?
A ONES account you can sign in with, and a Zapier account. You add the connection from the Apps page with + Add connection, pick ONES, sign in to it in the tab that opens and grant Zapier access. If your Zaps will read or write in projects you do not own yourself, your account needs read or write access on them. The connection is then reused by every step that touches ONES, so it is done once rather than once per Zap.
05Why does a ONES Zap keep running on its own?
Because it writes into what its own trigger watches. A Zap started by New Comment that runs Add Comment to Issue posts a comment, ONES reports that new comment, and the Zap starts again. The same goes for New Issue paired with Create Issue in the same project. Because the triggers are instant, the loop spins fast, and each round is a successful action, so a task. A filter that stops the Zap on what it wrote itself breaks the circle.
06What if the ONES action you need is not on Zapier?
Then this integration cannot do it, and no setting will add it. ONES on Zapier offers 3 triggers and 2 actions, and no search. No action edits, moves, closes or deletes an issue, and a Zap cannot look up an existing issue by itself: the issue it comments on has to come from an earlier step, usually the trigger. Sometimes rethinking the flow covers the gap, for example starting from Update Issue rather than searching. Past that, the work stays manual in ONES.
07Zapier, Make or n8n for ONES?
It depends on criteria, not on a ranking. First, the shape of your automations: if one trigger and one action cover the need, the Zapier free plan handles ONES with 100 tasks a month. Second, volume: every successful action is a task, and Update Issue can start a Zap often. Third, what is missing: ONES on Zapier has no search and no way to edit an issue. Check that the 5 operations listed here cover your need, then hold the other tools to the same three criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations