Triggers

A trigger is what starts a workflow. Think of it as the “when” in “when X happens, do Y”. Every workflow has one trigger card at the top of the canvas, and every time the trigger fires, the workflow runs once. For a list, that means once per row. Where: open a workflow → Build tab → click the first card on the canvas · https://connie.ai/<workspace-id>/workflows/<workflow-id>?tab=canvas

​

The four kinds of trigger

The AI Agent card in Add workflow creates a Schedule trigger with an AI Agent step. Outreach campaign creates a Run every row of a list trigger.

​

Choose or change the trigger

​

Run every row of a list

The workflow works through the rows on its Records tab, one run per row. Each row’s columns are available to your steps as variables under Record.

​

Add rows

Open the Records tab and use the Actions menu to:

• add records by hand,
• Import from CSV (up to 25 MB, with Skip duplicates (recommended) or Overwrite existing),
• Import from LinkedIn (a LinkedIn search, the comments or reactions on a post, a group, or an event),
• Import from CRM,
• Import from List, which mirrors one of your Records lists into the workflow without copying it. Edits write through to the list.
• or find new people and companies with Lead Finder.

​

Run it

Click Run in the top bar and choose:

• All rows, First 10 rows, First row only, or Selected rows (tick rows on the Records tab first).
• Run only on empty cells: skips steps that already have a result for a row. Use it to avoid paying twice when you re-run.
• Keep running on new rows: new rows added later (by import, list sync or by hand) run automatically. The button changes to Run and set live.

You can run at most 500 selected rows at once.

​

Trigger settings

• Recurring refresh: “Runs all of your items on a schedule instead of running them only once”. Shows schedule controls (Minute, Hourly, Daily, Weekly; no Monthly here). Here Minimum Interval starts at 15 minutes.
• Column Filters: “Only trigger when row matches these conditions”. Click Add filter.
• List sync (in Workflow settings): for each mirrored list, “When on, records added to this list are mirrored into the flow automatically.”

​

Event

The workflow runs every time a chosen event happens. When you pick Event, a picker opens with tabs All, Workflows, Email, Calls, Connectors and Webhooks, plus a Popular group. Task events (Task Created, Task Updated, Task Assigned, Task Status Changed, Task Completed, Task Due Soon, Task Overdue) aren’t on any of these tabs. Find them on the All tab, or search “Task”. You can stack several events on one workflow with Add trigger. Removing one asks “Delete event?”.

​

Event settings

Depending on the event, the panel offers:

• Connected Account: which account to listen to. Some events offer All connected accounts (N), which includes accounts you connect later. + Add account connects a new one.
• List (Record Created / Updated): “Runs when a record is added to the selected list.” Add Column Filters to narrow it down.
• Trigger Delay (record, task and Google Sheets events): wait up to 24 hours before running. After the delay, Connie re-checks that the record still matches your filters and uses its latest values.
• Email Received filters: From Filter (e.g. “@company.com”), Keyword Filter, Label Filter, Email Folder.
• Include conversation history (email and LinkedIn messages, on by default) and Only replies to a flow’s messages.
• Status changed to (task status events).
• Call Filters (call events): Sentiment, Recording Provider, Meeting Platform (Zoom, Google Meet, Microsoft Teams, Slack Huddle, Other), Minimum Duration, Has Competitor Mentions.
• Slack Channels, Google Calendar Calendar, Calendly Event type and Ignore reschedules, Google Docs Drive / Folder / Include subfolders, Google Sheets spreadsheet and Sheet (tab).

​

How quickly events arrive

• Record Created fires when a record is added to the selected list, not whenever a record is created anywhere. For a filtered (smart) list, it fires when a record starts matching.
• A bulk import fires one run per record. Importing 500 records into a watched list starts 500 runs.
• Google Sheets and Google Docs are checked about every 30 seconds while the workflow is live.
• Calendly triggers need a paid Calendly plan (Standard or above).
• For Slack, Connie’s bot joins the configured channels when you save. Private channels may need you to invite the bot.

​

Manually

A manual workflow runs when you click Run. You can give it a form, so each run asks for inputs (for example, a company domain to research). Each answer is available to later steps as a variable under the trigger. Manual workflows are never set live; every run is started by hand. Each manual run adds a new row to Runs.

​

Schedule

The workflow runs on a timer. Click the trigger card to set:

• Timezone: defaults to your browser’s timezone. “All times are in this timezone”.
• Run frequency: Minute, Hourly, Daily, Weekly or Monthly.
  • Weekly: Day of week (one day).
  • Monthly: Day of month (1st–31st). “Months without a 31st are skipped”.
  • Daily, Weekly, Monthly: Run at time, in whole hours.
  • Minute and Hourly: Maximum runs per day (default 10) and Minimum Interval in minutes (default 0). The time between runs is the longer of the frequency and the Minimum Interval.
• Stop flow if node fails (on by default): “When off, the flow keeps running the remaining nodes after a failure”.

Then click Run → Set live. A schedule never runs until the workflow is live. To try it once without going live, use Run only once now. There’s no field for a cron expression. A schedule made with one in the past shows as Custom: “This schedule can’t be edited here. It keeps running as is — choose a frequency above to replace it.”

​

Test a trigger

Some triggers can capture a real sample event, so later steps have example data to work with.

1. Click the trigger card → Capture test event (or open its Test panel) → Run Test.
2. Do the real thing: send an email to the connected account, add a row to the list, post to the webhook URL. The panel shows, for example, “We are now listening for emails to be received by …”.
3. Captured events are listed. Choose one with Use as test event for Run Once.

This works for Email Received, LinkedIn Message Received, Slack, Record Created / Updated, Google Calendar and Custom Webhook.

​

Good to know

• One trigger kind per workflow. You can stack several Event triggers, but not several schedules, forms or lists.
• Scheduled runs that overlap run at the same time. If a run is still going when the next one is due, both run.
• Maximum runs per day: once reached, later scheduled runs that day are skipped, with no row in Runs. Starting a run by hand still works.
• Running hours in Workflow settings can hold back event and webhook runs outside the hours you choose.
• Credits are checked before a workflow goes live, when a schedule is saved, and before each webhook run.
• Who can change triggers: anyone with edit access to the workflow.

​

Troubleshooting

​

Related

• Webhooks — start a workflow from any outside app
• Variables — use the trigger’s data in later steps
• Test and run — run once, set live, workflow settings
• Records lists — the lists that list-based workflows and record events use
• Connect accounts — connect Gmail, Slack, HubSpot and more