Resources · Zapier integration

AnnounceKit Zapier integrationAutomate AnnounceKit with Zapier.

The AnnounceKit Zapier integration gives you 4 triggers and 1 action, with no search step. Posts, comments, reactions and new subscribers can start a Zap, and a post can be written for you. Here is what each one does, what it costs and where it trips.

See the 5 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the AnnounceKit Zapier integration actually does

AnnounceKit is where you publish your product news, in a feed and a widget on your site. Zapier connects it to other tools: something happens in AnnounceKit, Zapier sees it and runs the next step. The link works both ways, but not evenly: four events can start an automation, and only one thing can be written back.

Three results people build first. A release note relay: a post written in one project lands as a draft in another, through New Post and Create Post. A feedback inbox: every comment or reaction on your announcements reaches the tool your product team already reads, through New Comment and New Reaction. A subscriber handoff: each person who signs up for your updates gets passed to your email or CRM tool, through New Subscriber.

Now the part the app page leaves out. Zapier cannot edit, delete or look up an existing post here. There is no search step at all, so a Zap can never fetch an older announcement to reuse it. Every trigger checks on a timer, none of them is instant, so on the free plan nothing moves faster than the 15-minute check. And each trigger asks you to pick one project: a Zap watches a single project, never your whole account.

If you are weighing tools, the same app has an AnnounceKit Make integration, and the n8n vs Zapier comparison is there for the bigger choice of tool.

Vocabulary

The Zapier words you need, in one minute

Zapier has its own vocabulary. Seven words cover everything on this page.

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 sits and waits for that event, here a new post or a new subscriber.
Action
What the Zap does once it has started: the step that writes, sends or moves something for you, like creating a post.
Task
The unit Zapier bills you for. One task is one action your Zap carried out successfully; your plan counts those, nothing else.
Polling vs instant
A polling trigger is checked on a timer, Zapier asks for new items at a fixed interval. An instant one is reported by the app the moment it happens.
Filter
A step that lets the Zap carry on only when what arrived meets a condition you set, and stops it quietly otherwise.
Connection
Your AnnounceKit account linked to Zapier once, then reused by every step and every Zap that touches AnnounceKit.
Cost

What an AnnounceKit Zap really costs

AnnounceKit is not a premium app, so it works from the free plan. Watching for posts or comments costs nothing, however often Zapier checks.

  • Premium appNo, works on the free plan
  • Free plan100 tasks a month, two-step Zaps
  • Trigger checksFree of charge, never a task
  • Instant triggersNone, all 4 are polling

You pay in tasks, and only when an action succeeds: one post created is one task, a failed attempt is not counted. The free plan gives you 100 tasks a month, unlimited Zaps, and a check every 15 minutes. The catch is size: free Zaps have two steps, one trigger and one action. Add the filter from the example above and the Zap becomes multi-step, which needs a paid plan. Each action you add on top is billed on its own.

Connect

Connect AnnounceKit to Zapier in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. Before that, make sure you have an AnnounceKit account, and access to any project you do not own but want the Zap to touch.

  2. 02

    Pick AnnounceKit

    Type AnnounceKit in the search box of the dialog, select it, then click Add connection. A new tab opens on the AnnounceKit side, where the rest of the setup happens, with your usual AnnounceKit login.

  3. 03

    Sign in and allow access

    Log in to AnnounceKit in that tab and grant Zapier access to the account. From then on, every AnnounceKit step in every Zap reuses this same connection.

First Zap

Your first Zap: relay release notes to the public project

GoalYour team writes every change in an internal AnnounceKit project. Only the ones tagged [public] in the title should reach the customer widget, as drafts someone reviews before they go live.

  1. 01

    Build the trigger

    In Build, choose AnnounceKit and the New Post event, then pick the internal project. That project is the only one this Zap will ever watch.

  2. 02

    Test it on a real post

    Click test: Zapier brings back the three most recent posts of that project. Pick one that carries the [public] tag so the next steps have real data to map.

  3. 03

    Add the filter

    Add a Filter step: the post title field, a text rule "contains", value [public]. Write the tag when you create the post, since each post is seen only once.

  4. 04

    Add the action

    Pick Create Post, choose the public project, map the title and the body from the trigger, and switch on Create as Draft so nobody publishes by accident.

  5. 05

    Test, then publish

    Run the action test, open AnnounceKit and check the draft. Then click Publish to switch the Zap on. A filter makes this Zap multi-step, so it needs a paid plan.

Triggers

AnnounceKit triggers

4 events start a Zap when something happens in AnnounceKit. Zapier checks for them at the interval your plan allows.

1

New Post

Polling trigger

In Zapier“Triggers when a new draft or published post is created.”

Starts your Zap each time a post appears in the project you picked, whether it was saved as a draft or published straight away. That makes it the natural starting point for anything that copies, announces or archives your updates elsewhere.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a product manager wants every new changelog entry posted to the team chat without copying it by hand.
Watch out
drafts count too, so add a filter if only finished posts should go out, and pick the right project since the field is required.
2

New Comment

Polling trigger

In Zapier“Triggers on new comment”

Fires when a reader leaves a comment on one of your announcements in the chosen project. It is how feedback written under a release note leaves AnnounceKit and reaches the people who can answer it.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a support lead wants each comment on a new feature turned into a ticket in the helpdesk the team already works from.
Watch out
the Zap only covers the one project you select; comments on other projects need their own Zap.
3

New Reaction

Polling trigger

In Zapier“Triggers on new reaction”

Picks up each reaction readers leave on your posts in one project. Reactions are the lightest signal you get from users, and this trigger lets you log them somewhere you can count and compare them over time.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a product marketer adds each reaction as a row in a tracking sheet to see which announcements land.
Watch out
every reaction is a separate run, and each action that follows costs a task, so a popular post can eat into a free plan.
4

New Subscriber

Polling trigger

In Zapier“Triggers when somebody subscribes to the project.”

Runs when someone subscribes to the project you picked to hear about your updates. It turns your announcement feed into a small source of interested contacts for other tools.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a growth marketer sends every new subscriber to the CRM so sales can see who follows the product closely.
Watch out
people who subscribed before you switched the Zap on are not sent over; the Zap starts from the day it goes live.
Actions

AnnounceKit actions

AnnounceKit gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Post

Action

In Zapier“Creates a new post.”

Writes a new post in the AnnounceKit project you choose, with a title and a body you fill from earlier steps. The body accepts HTML, so formatting from another tool can come through.

When to use it
a release in your project tracker should open a ready-to-edit announcement.
Watch out
Project, Post Title and Post Body are all required, and Create as Draft keeps the post away from readers until someone checks it.
When it breaks

When an AnnounceKit Zap breaks

Zapier attaches no help article to AnnounceKit, so the problems below are the general ones of any Zap, seen through this app.

None of them shows up as an error on day one. They show up later, as a missing post, a doubled one, or a task count that runs out early. If you get stuck, the Zapier troubleshooting guide is the next stop when the cause is not on this list.

  • Old posts never come through

    A Zap only reacts to what happens after you switch it on. Past posts, comments and subscribers stay where they are; moving that backlog is a separate job.

  • The Zap feeds itself

    Point New Post and Create Post at the same project and each created post sets the Zap off again. Always write into a different project than the one you watch.

  • A bulk import gets held back

    If a project suddenly returns a large batch of posts at once, after an import or a migration, Zapier's flood protection can hold the run back.

  • The same item twice? Not here

    Zapier remembers what a polling trigger has already seen, so one post or comment does not start the Zap twice. A duplicate usually means two Zaps watch the same project.
Need help

Need help automating AnnounceKit with Zapier?

A person reads every message.

FAQ

AnnounceKit Zapier integration: common questions

01Is the AnnounceKit Zapier integration free?
Yes, it works on the free plan. AnnounceKit is not a premium app, so you do not need a paid plan just to connect it. The free plan comes with 100 tasks a month and unlimited Zaps, but each Zap stays at two steps: one trigger and one action. As soon as you add a filter, a second action or any extra step, the Zap becomes multi-step and you need a paid plan.
02How many Zapier tasks does an AnnounceKit Zap use?
One task per successful action, nothing for the trigger. If a new comment starts your Zap and it creates one item somewhere else, that run costs one task. A Zap with three actions costs three tasks each time it runs. Checking AnnounceKit for new posts or subscribers costs nothing, however often Zapier looks, and an action that fails is not counted. Busy projects with many reactions are where the count climbs fastest.
03Does AnnounceKit trigger Zaps in real time?
No. All four AnnounceKit triggers are polling triggers: Zapier goes to check for new items at a fixed interval. On the free plan that check runs every 15 minutes, on Professional every 2 minutes, and on Team and Enterprise every minute. On paid plans you can change how often it checks and run a check by hand from the editor. The app offers no instant trigger, so this delay cannot be removed from the editor.
04What does it take to connect AnnounceKit to Zapier?
An AnnounceKit account, plus access to every project you want the Zap to watch or write into. You add the connection from the Apps page of Zapier with + Add connection, sign in to AnnounceKit in the tab that opens and grant access. Every operation asks you to pick a project, so the account you connect must see that project. One connection then serves every Zap that uses AnnounceKit, so there is nothing to redo when you build a second or a third one.
05Why does a Create Post Zap keep creating posts in a loop?
Because it writes into the project its own trigger watches. If New Post and Create Post point at the same project, each new post starts the Zap, which creates another post, which starts it again. That burns your tasks fast. The fix is simple: always watch one project and write into a different one, and add a filter on the title so only the posts you tagged go through. Test it once on a real post before you publish.
06What if the AnnounceKit operation you want is not there?
Then Zapier cannot do it for this app today. The integration covers four triggers and one action, Create Post, with no search and no way to edit or delete a post. For anything else, look at the AnnounceKit side, or at another automation tool that may expose more of the app. Checking the operation list before you build saves a Zap that can never be finished, and the time spent mapping fields for nothing.
07Zapier, Make or n8n for AnnounceKit?
It depends on your criteria, not on a winner. Zapier is the quickest route if the four triggers and Create Post cover your need and you want to stay on a hosted tool with a free plan. Make is worth a look if you build longer scenarios with many steps. n8n suits teams that want to host the automation themselves and accept more setup. Compare the operations each one offers for AnnounceKit before you choose.
Same platform

Other docs you might need on this stack.

Browse all integrations