Make a real campaign blocker visible
Mark the card blocked when a confirmed dependency is stopping progress, so the team can respond to the right obstacle.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Set card block reason
Tool to block a Kanbanize card by setting a block reason. Use when you need to mark a card as blocked and specify the reason preventing progress.
Why this helps
A stalled campaign can look like ordinary in-progress work, delaying help and making follow-up harder.
- Makes a confirmed blocker visible on the card.
- Helps collaborators focus on the dependency preventing progress.
- Reduces the need to explain the same stalled status repeatedly.
Setup
Build it in a few focused steps.
- 1Connect Klaviyo and Kanbanize to Notis once through the portal.
- 2Create an automation in the portal or ask Notis to mark matching campaign work blocked when a confirmed dependency is reported.
- 3Use one plain-language prompt that tells Notis to set the supplied valid block reason on the matching card only when progress is actually prevented.
- 4Choose an incoming webhook trigger and a channel for run reports.
- 5Test with a real blocked example and verify the reason on the card.
Questions about this workflow
Should every campaign delay be marked blocked?
No. Use this when a confirmed dependency is preventing progress and the board has the appropriate block reason.
Does Notis invent a block reason?
The prompt should use a valid reason available on the board and supplied or confirmed in the incoming context.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Klaviyo to Kanbanize. A trigger fires from one place; an action lands in another.
Klaviyo triggers
Kanbanize actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add a comment to a card
Tool to add a comment to a Kanbanize card. Use when you need to add notes, updates, or any text-based information to an existing card.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Check Board Milestone
Tool to check if a milestone is available on the specified board. Use when you need to verify milestone existence on a specific board. Returns True if the milestone is available (HTTP 204), False if not found (HTTP 404).
Check User Is Card Watcher
Tool to check if a user is a watcher of a specific card. Use when you need to verify if a user is watching a card.
Delete Board
Tool to delete a board by its ID. Use when you need to permanently remove a board from Kanbanize. Note: The board must be archived before deletion.
Delete Card
Tool to delete a card from the Kanbanize board. Use when you need to permanently remove a card and all its associated data from the board.
Delete Tag
Tool to delete a tag from Kanbanize. Use when removing a tag and optionally replacing it with another tag for all affected cards.
Delete Workflow
Tool to delete a workflow for the specified board. Use when you need to permanently remove a workflow from a board.
Get Board Block Reasons
Tool to get a list of block reasons available on a board. Use when you need to retrieve available block reasons for a specific board.
Connect any two apps with Notis in the middle.
Klaviyo and Kanbanize, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Kanbanize.