Flock Zapier integrationAutomate Flock with Zapier.
The Flock Zapier integration posts messages into Flock for you. It has 0 triggers, 2 actions and 0 searches, so Flock always sits at the end of the Zap: another app reports an event, and Flock gets the message, in a channel or in your own chat.
Verified Trustpilot reviews · AI, automation & growth agency
What the Flock Zapier integration does for your team
Flock is a team chat app. Through Zapier, it can only receive: a Zap (the automation you build on Zapier) starts in some other app, then posts a message into Flock. Two outcomes are possible, a message in a channel your team reads, or a private note in your own chat. Nothing more, nothing less.
Three results teams usually build with it. First, a shared alert feed: every new form entry, signed deal or support ticket becomes a line in a channel, through Send Channel Message. The team stops checking five tools to know what happened. Second, a personal inbox for automations: Send Direct Message posts to yourself, so a payment, a calendar booking or a file upload pings only you, without noise for colleagues. Third, a handoff signal: when a step in another app finishes, the channel of the next team hears about it right away, with the details written into the message text.
Now what Zapier does not do for Flock, and it matters before you plan anything. No event inside Flock can start a Zap: a new message, a new channel member or a finished poll will never set off an automation, because the app exposes zero triggers on Zapier. There is no search either, so a Zap cannot look up a Flock user or read an older message. And the two actions only post text: their fields are a message and a channel, nothing about files, polls, to-dos or reminders. If your plan relies on any of those, Zapier is the wrong path for that part.
If you are weighing tools, the Flock Make integration page and the Make vs Zapier comparison are the next reads.
Zapier vocabulary in one minute
Seven words cover everything on this page. Each one is used later without another explanation.
- Zap
- Your automation on Zapier: one starting event, then one or more steps that run every single time that event happens.
- Trigger
- The event in an app that starts the Zap. Flock has none, so the trigger always comes from another app you connect.
- Action
- What the Zap does once started, like writing or sending something. Both Flock operations are actions that post a message.
- Task
- The unit Zapier bills: one action that completes successfully. Your plan's monthly quota counts these and nothing else.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer. An instant trigger is pushed by the app the moment the event happens.
- Filter
- A step that lets the Zap continue only when the incoming data meets your condition, and quietly stops it otherwise.
- Connection
- Your Flock account linked to Zapier once, then reused by every step in every Zap that posts to Flock.
What a Flock Zap really costs
Flock is not a premium app, so it works on the free plan. The bill comes from actions, not from waiting.
- Free plan tasks100 per month
- Premium appNo, Flock runs on the free plan
- Free plan Zap size2 steps: one trigger, one action
- BilledEach message posted successfully
Each message Flock receives successfully counts as one task. The trigger never costs anything, however often Zapier checks the other app, and a message that fails to post is not counted. The catch on the free plan: Zaps stop at two steps, one trigger and one action. Add a filter, or a second Flock message, and you have a multi-step Zap, which needs a paid plan. Two messages for the same event also mean two tasks per run.
Connect Flock to Zapier in 3 steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. A dialog opens with a search box. Type Flock and pick it from the list, then confirm with Add connection.
- 02
Sign in to Flock
A new tab asks you to log in to Flock. Use the account that already belongs to the channels your Zaps will post in, since every Flock step in your Zaps will act through it.
- 03
Grant access
Approve the access request so Zapier can post on behalf of that account. The connection is now saved once and shows up in the account list of any Flock step you add later, in any Zap.
Your first Zap: new Typeform entries posted to a Flock channel
GoalEvery new Typeform entry that asks for a demo shows up in your sales channel in Flock, with the contact details in the message.
- 01
Build the trigger
Create a Zap and pick Typeform as the starting app with New Entry as the event. Connect your Typeform account and choose the form that collects requests.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent entries of that form, so you can see real answers and spot the one that says what the visitor wants.
- 03
Add the filter
Click the plus icon, choose Filter, then set the field, the rule and the value. Pick a text rule for a text answer. This step makes the Zap multi-step, so it needs a paid plan.
- 04
Add the Flock action
Add Flock with Send Channel Message, select your Flock connection, choose the sales channel, then write the Message and insert the name and email from the Typeform test entry.
- 05
Test and publish
Test the Flock step and check that the message really appears in the channel. If it reads well, click Publish to switch the Zap on for every entry that arrives from now on.
The 2 Flock actions on Zapier
Flock gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Send Direct Message
ActionIn Zapier“Post a new message to yourself.”
This one writes into your own Flock chat, addressed to the connected account and to nobody else. You only fill in the Message, and you can mix fixed words with data from earlier steps.
Send Channel Message
ActionIn Zapier“Post a new message to a channel you choose.”
Here the Zap posts into a channel you choose, where everyone in it can read the update. Two fields are required: the Channel and the Message text.
When a Flock Zap stops posting
Zapier links no help article to Flock, and no Flock-specific limit is documented. What breaks comes from Zapier itself.
Four situations explain most surprises. None of them is a bug in Flock, and each one has a simple workaround once you know it exists. For deeper cases, Zapier troubleshooting is the next stop.
Old events never arrive
A Zap only reacts to what happens after you publish it. Entries or orders created before that day will not be posted to Flock. Moving the backlog is a separate job.A big import gets held back
If the trigger app suddenly returns a huge batch, after a migration or a bulk import, Zapier's flood protection can hold those items back instead of posting them all to Flock.The filter never lets anything through
Filter rules are typed. A number rule on a text answer, or the reverse, never passes, so no message reaches Flock. Match the rule type to the value you saw in the test.The free plan refuses the second step
The free plan builds two-step Zaps only. A filter, or a second Flock message after the first, turns the Zap multi-step, and it then needs a paid plan to run.
Need help automating Flock with Zapier?
A person reads every message.
