Summary

Besides the Catch Webhook and Schedule triggers, Flows can start from events inside Alta itself. The Alta trigger family fires the moment something happens to your prospects — a new prospect is created, someone replies, an outcome or status changes, a call completes, or a LinkedIn connection request is accepted. Pick one as your Flow's trigger and react in real time.

Who this is for

Anyone automating around campaign activity — RevOps syncing replies into a CRM, sales leaders posting "Meeting Booked" wins to Slack, or ops teams logging completed calls, without polling or webhooks.

Before you start

You need permission to create Flows (the sidebar item is Workflows, route /workflows).
A Flow only runs when it's Published and toggled Active — drafts never fire.
No connection or API key is needed. Alta triggers are built in.

Step 1: Add the trigger

In the sidebar, click Workflows, then open or create a Flow.
Click the trigger node on the canvas and choose Alta from the integration list.
Pick one of the six event triggers (details below). Every Flow has exactly one trigger.

Step 2: Pick the right event

Prospect Created

Fires when a new prospect is created. Output: Prospect ID.

Prospect Human Reply

Fires when a prospect replies with a human (non-automated) message. Optional Channel filter — the field hint reads "leave blank if you don't want to filter by channel". Channel options: email, linkedin, call, sms, whatsapp. Outputs: Prospect ID, Channel, Text (the reply body), and Message ID.

Prospect Outcome Changed

Fires whenever a prospect's outcome changes. Output: Prospect ID. Use it when you care that something changed and will look up the details yourself.

Prospect Status Changed

Fires when a prospect's status changes, and also tells you what it changed to. Optional Status filter with these options: New, Pending Outreach, Pending Reply, Interested, Not Interested, Meeting Booked, Unclassified, No Response, Bounced / Invalid. Outputs: Prospect ID and New Status.

Call Completed

Fires when a call finishes. Output: Call ID.

Linkedin Connection Request Accepted

Fires when a prospect accepts your LinkedIn connection request. Output: Prospect ID.

Step 3: Enrich the payload

Event payloads are intentionally lean — mostly IDs. Add an Alta action right after the trigger to pull the full record:

Get Prospect — takes Prospect ID (required) and returns the prospect's Prospect ID, Person ID, Campaign ID, and Created At.
Get Person — turn the Person ID into name, title, and contact details.
Get Call — turn a Call ID from Call Completed into the call record.

Pipe the trigger's output into these actions with the variable picker, then send the enriched data wherever you need — Slack, your CRM, or an AI step.

Step 4: Publish and toggle Active

Click Publish, then make sure the Flow's Status switch on the Workflows tab is set to Active. From then on, every matching event starts a run — check the Runs tab to see each one with per-step inputs and outputs.

Tips and common pitfalls

Filters drop events silently. If you set a Channel or Status filter and the event doesn't match, the Flow simply doesn't run — no failed run appears. Leave the filter blank to catch everything.
Outcome vs. Status. Prospect Status Changed includes the New Status output and supports filtering; Prospect Outcome Changed only signals that a change happened. If you want to branch on the new value, use Status Changed.
One status per trigger filter. The Status filter accepts a single value. To react to several statuses, leave it blank and use a Router step to branch on New Status.
Test uses real data. When you test the trigger in the editor, Alta samples a real prospect from your account to populate the variable picker — handy for mapping fields before publishing.
Reply text is right in the payload. Prospect Human Reply includes the reply Text, so you can classify or summarize it with an AI action without an extra lookup.
Drafts never fire. If events aren't triggering runs, check the badge in the editor — the Flow must be Published, and its Status switch Active.