Triggers
Triggers are the events that start your automation workflows. When a trigger event occurs in your workspace, any active workflow connected to that trigger will execute. Flokan provides 21 triggers organized into four categories: Card Events, Content Events, Board Events, and Workspace Events.
Card Events
Card triggers fire when something happens to a card on any board in your workspace (or on a specific board, depending on how you configure the trigger).
Card Created
Fires when a new card is added to any list on a board.
Available data:
- Card title, description, and ID
- The list the card was created in
- The board the card belongs to
- The user who created the card
- Creation timestamp
Common use cases:
- Notify the team in Discord/Slack when a new video idea is added
- Assign a default checklist to every new card
- Log new cards to an external project tracker via webhook
Card Updated
Fires when any card property is modified — title, description, due date, labels, assignees, or custom fields.
Available data:
- The card's old and new values for the changed property
- Which field was changed
- The user who made the change
- Update timestamp
Common use cases:
- Notify assignees when a card they're working on is updated
- Track changes to high-priority cards
- Sync card data to external systems
Card Assigned
Fires when a team member is assigned to (or unassigned from) a card.
Available data:
- The card details
- The assigned/unassigned user
- The user who made the assignment change
- The board and list context
Common use cases:
- Send a DM to the assigned person with card details
- Add the assigned person to a related Discord channel
- Update a team workload dashboard
Card Moved
Fires when a card is moved from one list to another — the most commonly used trigger for production pipeline automations.
Available data:
- Card details
- Source list (where the card was)
- Destination list (where the card moved to)
- The user who moved the card
- The board context
Common use cases:
- When a card moves to "Published," announce it in Discord
- When a card moves to "Editing," notify the editor
- When a card moves to "Review," assign the reviewer and set a due date
- When a card moves to "Thumbnail," create a task in the Thumbnail Pipeline
Card Deleted
Fires when a card is permanently deleted from a board.
Available data:
- The deleted card's details (captured before deletion)
- The user who deleted it
- The board and list it was deleted from
Common use cases:
- Log deletions for audit purposes
- Notify the team when a card is removed
Card Due Soon
Fires when a card's due date is approaching (within the configured "due soon" window).
Available data:
- Card details including the due date
- How much time remains until the due date
- Current assignees
Common use cases:
- Send a reminder DM to assignees
- Post a reminder in the team Discord channel
- Escalate by notifying a manager if the card is high priority
Card Overdue
Fires when a card's due date has passed and the card hasn't been moved to a completed status.
Available data:
- Card details including the overdue due date
- How long the card has been overdue
- Current assignees
Common use cases:
- Send escalation notifications
- Automatically add an "Overdue" label to the card
- Notify the team lead or manager
Content Events
Content triggers fire when production assets are attached to cards.
Attachment Uploaded
Fires when any file is uploaded to a card as an attachment.
Available data: Card details, file name, file type, file size, the uploader, and timestamp.
Script Added
Fires when a script is attached to a card. Available data: Card details, script information, the uploader.
Common use case: Notify the editor that a script is ready for review.
Thumbnail Added
Fires when a thumbnail image is uploaded to a card. Available data: Card details, thumbnail URL, thumbnail name, the uploader.
Common use case: Notify the thumbnail reviewer that a new version is ready.
Video Added
Fires when a video file is linked to a card. Available data: Card details, video information, the uploader.
Common use case: Notify the team that a video is ready for review.
Voiceover Added
Fires when a voiceover recording is attached to a card. Available data: Card details, voiceover information, the uploader.
Common use case: Trigger the VO-to-Images pipeline or notify the editor.
Board Events
Board triggers fire when changes happen at the board level.
Board Created
Fires when a new board is created in the workspace. Available data: Board name, description, the creator, creation timestamp.
Board Deleted
Fires when a board is deleted. Available data: Board details (captured before deletion), the user who deleted it.
Board Member Added
Fires when a user is added to a board. Available data: Board details, the added member, who added them, their board role.
Common use case: Grant the new member access to a related Discord channel.
Board Member Removed
Fires when a user is removed from a board. Available data: Board details, the removed member, who removed them.
Common use case: Revoke Discord channel access for the removed member.
Member Role Changed (Board)
Fires when a member's role on a specific board is changed. Available data: Board details, the member, old role, new role, who changed it.
Workspace Events
Workspace triggers fire when changes happen at the workspace level.
Workspace Deleted
Fires when the workspace is deleted. Available data: Workspace details, the user who deleted it.
Workspace Member Added
Fires when a new user joins the workspace (via invite or link). Available data: The new member's details, who invited them, their assigned role.
Common use case: Send a welcome DM, assign to default Discord channels, add to onboarding board.
Workspace Member Removed
Fires when a member leaves or is removed from the workspace. Available data: The removed member's details, who removed them (or if they left voluntarily).
Common use case: Revoke Discord roles and channel access.
Member Role Changed (Workspace)
Fires when a member's workspace role is changed. Available data: The member, old role, new role, who changed it.
Common use case: Sync the role change to Discord by assigning/removing Discord roles.
Each trigger provides data that can be used in subsequent actions. When configuring actions, you can reference trigger data using the variable picker — for example, the card title or the user's name.