Using flow triggers
Run flows automatically when new content arrives.
Triggers let you run a flow automatically whenever new content is added to your workspace. Instead of clicking Run each time, you set up a trigger once and Klang handles the rest — every new upload that matches your criteria gets processed by the flow.
Create a trigger
- In the top-left corner, click the Klang button to open the menu

- Click Flows
- Open the flow you want to automate, or pick a template
- Click Automate

The trigger setup dialog opens.
Configure the trigger

The dialog walks you through a few steps:
Choose what starts the flow
Select when the flow should run:
- All your new files — The flow runs on every new upload in your workspace (transcriptions, PDFs, meetings)
- Uploads in a specific folder — The flow only runs when files are uploaded to the folder you choose
If you select a specific folder, a folder picker appears. Choose the folder you want to monitor.
Filter by labels
By default, the trigger runs on all files that match your scope. To narrow it down:
- Under the label filter, select Specific labels
- Choose one or more labels from the list

The flow will only run on files that have at least one of the selected labels applied.
Name your trigger
Give the trigger a name that describes what it does, for example “Summarize client meetings to Slack” or “Export interview notes to Drive”. This name appears in your triggers list.
Configure output settings
If the flow sends results somewhere (Slack, Google Drive, OneDrive, email), you may need to configure those settings in the same dialog. For example, choose which Slack channel to post to or which Drive folder to save in.
Activate the trigger
When you click Create automation, the trigger is created and starts running immediately. Every new file that matches your criteria will be processed by the flow.

Manage your triggers
View all triggers
On the Flows page, your active triggers appear in the triggers list. Each trigger shows its name, status, and when it last ran.
Pause and resume
On the trigger detail page, click Pause to stop the trigger from running. Click Resume to start it again. Pausing does not delete the trigger or its settings.

Edit a trigger
- On the triggers list, click the three-dot menu next to the trigger
- Click Edit
- Change the name, folder, labels, or output settings
- Click Save changes
Delete a trigger
- On the triggers list, click the three-dot menu next to the trigger
- Click Delete
- Confirm the deletion
Deleting a trigger does not affect files that were already processed.
Activity log
Each trigger keeps a log of every time it ran. The activity log shows:
- Triggered by — What started the run (upload, specific folder)
- File — The file that was processed
- Destination — Where the result was sent (Slack, Drive, document)
- Started — When the run began
- Status — Whether the run completed, is in progress, or failed
If a run fails, the status column shows the reason. The most common cause is insufficient credits.
Tips
- You can only have one trigger per flow. To process files differently, create separate flows with their own triggers.
- Triggers use credits each time they run. Make sure your workspace has enough credits for the volume of files you expect.
- If you no longer need a trigger, pause or delete it to avoid using credits on files you do not need processed.
Was this article helpful?
Your feedback helps us improve our documentation.
Suggested Articles
Need more help?
Our support team is here to help you.