Send a Slack alert when a Ziflow proof status changes

Whenever a Ziflow proof’s status changes, this workflow posts a message to a Slack channel with the proof details you map, so reviewers and project owners hear about it without opening Ziflow.

Ziflow

Slack

Download this workflow Browse more workflows

2 steps Setup ~5 min Used on 3.4k sites Free to import

The Send a Slack alert when a Ziflow proof status changes workflow on the FlowMattic canvas, with 2 steps across Ziflow, Slack — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

Proof reviews move in small steps, and people outside the review often only care about where a proof stands. Checking Ziflow for each change is easy to forget. This workflow brings each status change into Slack, where the team already talks about the project.

The Ziflow trigger, Proof Status Changed, fires whenever a proof's status is changed. FlowMattic passes the proof data from that event to the Slack step, Send Channel Message, which posts to the channel you pick. You write the message and map in proof details such as its name and new status.

Every status change sends a message, whatever the new status is. If your proofs pass through many statuses, the channel gets one post for each. Add a Filter after the trigger if you only want certain statuses posted. Nothing is written back to Ziflow, and Task History shows each run.

Client approvals in an agency channel

Account managers watch one Slack channel per client. A post appears there whenever that client's proof moves to a new status, so nobody has to ask in the thread.

Production hand-off

The print or development team follows the alerts channel and can see when a proof's status changes, then checks Ziflow before starting work.

Weekly review meeting prep

The channel's history shows every status change in order, which gives the project lead a quick record to scroll through before the meeting.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
Ziflow Proof Status Changed
Fires when the status of a proof is changed in Ziflow. The proof data from that event is passed to Slack so you can map it into the message.
Step 2Action
Slack Send Channel Message
Posts the proof update to a Slack channel of your choosing. Write the text and map Ziflow details such as the proof name and its new status.

What you need

FlowMatticCore
Ziflow AccountAccount
Slack AccountAccount

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

Add a Filter after the trigger that continues only when the status field equals the value you care about, such as approved, if the channel should not hear about every change.
Include the proof's link in the message if the trigger returns one, so people can open it from Slack.
Reviews kept in a private Slack channel need the Send Private Channel Message action in place of this step, and an alert for a single reviewer fits Slack's Send Direct Message action.

Questions about this workflow

Which Ziflow status changes send a Slack message?

All of them. The template has no Filter, so every Proof Status Changed event posts to Slack. Add a Filter on the status field to narrow it down.

Can the Ziflow alert go to a private Slack channel?

The imported step posts to channels with Send Channel Message. The Slack app in FlowMattic has a separate Send Private Channel Message action for private ones, so swap the step if your proof channel is private.

Does this tell Slack about comments on a Ziflow proof?

No. It reacts to status changes only. Ziflow has other FlowMattic triggers, such as Comments & Replies and @Mentions, that you could use in another workflow.

What proof details can the Slack message include?

Whatever the Proof Status Changed event returns. After import, change a test proof's status in Ziflow and look at the captured data to see the available fields.