Actions
Actions are the steps that execute when a workflow's trigger fires. Flokan provides 33+ actions spanning core logic, Discord server management, Slack messaging, email, webhooks, and more. Actions can be chained together — the output of one action can be used as input for the next.
Core Actions
These actions provide fundamental workflow building blocks.
Condition
Branch your workflow based on data values. A condition evaluates an expression and routes the workflow down different paths based on whether the condition is true or false.
Example: "If the card has the label 'High Priority', send a Discord DM to the manager. Otherwise, just post in the general channel."
Conditions can evaluate:
- Trigger data (card title, list name, user, etc.)
- Output from previous actions
- String comparisons, numeric comparisons, and boolean checks
Delay
Pause the workflow for a specified duration before continuing to the next action. Delays are useful for:
- Reminder workflows — Wait 24 hours, then check if a card is still in "Review"
- Rate limiting — Avoid spamming notifications by waiting between messages
- Scheduled follow-ups — Wait a set time after an event before taking action
Configure delays in seconds, minutes, hours, or days.
Data Transform
Manipulate and reshape data between steps. Use this to:
- Extract specific fields from complex trigger data
- Format text (combine fields, change case, format dates)
- Convert data types
- Build structured payloads for webhook actions
Announcement
Send an internal notification to workspace members. Announcements appear in Flokan's notification system and can be targeted to specific users or roles.
Send an email to one or more recipients. Configure:
- To — One or more email addresses (can use trigger data, e.g., the card assignee's email)
- Subject — Email subject line with variable interpolation
- Body — Email body with rich text and variables
Webhook
Make an HTTP request to any external URL. This is the most flexible action — it lets you integrate Flokan with virtually any external service that has an API.
Configuration:
- URL — The endpoint to call
- Method — GET, POST, PUT, PATCH, DELETE
- Headers — Custom HTTP headers (e.g., authentication tokens)
- Body — JSON payload with variable interpolation
Common use cases:
- Notify a custom app when a card status changes
- Create tasks in external project management tools
- Log events to analytics platforms
- Trigger external CI/CD pipelines
Discord Actions
Discord actions require connecting your Discord server in Settings → Discord. All Discord actions use the server connection and user mappings configured there.
Flokan provides 17 Discord-specific actions, making it the most comprehensive Discord integration of any YouTube production tool.
Messaging
| Action | Description |
|---|---|
| Send Channel Message | Post a message to a specific Discord text channel. Messages support rich formatting, embeds, and variable interpolation from trigger data. |
| Send DM | Send a direct message to a mapped Discord user. The recipient is identified by their Flokan-to-Discord user mapping. |
Channel Management
| Action | Description |
|---|---|
| Create Channel | Create a new text or voice channel in your Discord server. Specify the channel name, category, and permissions. |
| Delete Channel | Remove a channel from the server. Use with caution — channel deletion is permanent. |
| Create Category | Create a new channel category for organizing channels. |
| Add Member to Channel | Grant a specific user access to a private channel. |
| Remove Member from Channel | Revoke a user's access to a private channel. |
| Remove User from Multiple Channels | Bulk-remove a user from several channels at once. Useful for offboarding. |
| List Channels | Retrieve a list of all channels in the server. Output can be used by subsequent actions. |
Role Management
| Action | Description |
|---|---|
| Create Role | Create a new Discord role with specified name, color, and permissions. |
| Delete Role | Remove a Discord role from the server. |
| Assign Role to User | Give a Discord role to a specific user. |
| Remove Role from User | Remove a Discord role from a specific user. |
Sync Operations
| Action | Description |
|---|---|
| Sync Channel to Users | Grant multiple users access to a specific channel in one operation. Useful for setting up project-specific channels. |
| Sync User to Channels | Grant a single user access to multiple channels at once. Useful for onboarding new team members. |
Data Operations
| Action | Description |
|---|---|
| Get User Mapping | Look up the Discord ↔ Flokan user mapping for a specific user. Returns the Discord user ID for a given Flokan user. |
| Get Workspace Mapping | Get the workspace ↔ Discord server mapping. Returns the connected server's details. |
| Save Mapping | Store a new user mapping between a Flokan member and a Discord user. |
Slack Actions
Slack actions require connecting your Slack workspace in Settings → Slack.
| Action | Description |
|---|---|
| Send Channel Message | Post a message to a Slack channel. Messages support formatting and variable interpolation. |
| Send DM | Send a direct message to a mapped Slack user. |
Chaining Actions
Actions can be chained in sequence, with each action's output available to subsequent actions. For example:
- Trigger: Card moved to "Published"
- Action 1: Get User Mapping (find the card assignee's Discord ID)
- Action 2: Send Channel Message (announce in #releases using card title and assignee name)
- Action 3: Send DM (congratulate the assignee)
- Action 4: Webhook (update external analytics dashboard)
Each action can reference data from the trigger and from any previous action's output using variable syntax.
Error Handling
When an action fails (e.g., a webhook returns an error, a Discord API call fails), the failure is logged in the workflow's run history with full error details. Subsequent actions in the chain may still execute depending on the workflow configuration.