Workflows for the meeting lifecycle

Every meeting.Everyone in sync.

Automate email, Slack, and webhook notifications around your meetings. Keep reps informed from the first booking to the follow-up.

The right update.
At the right moment.

Choose a booking event, select the routers or links it applies to, and decide what happens next. Let the routine updates take care of themselves.

Distro workflow card showing a form-submitted trigger, Slack action, all form routers, and active status — Distro workflow card · A form submission triggers a Slack notification.

Follow the meeting lifecycle

Trigger updates when meetings are booked, rescheduled, cancelled, completed, or marked as a no-show.

Choose where it runs

Apply a workflow to all sources of a supported type, or select specific routers and booking links.

Stay ready before.
Stay connected after.

Send your team a heads-up before a meeting and a follow-up prompt after it ends. Set the timing around the meeting itself.

Illustrative examples · Separate workflows can run before, after, or when a meeting changes.

Set the timing

Choose how many minutes before or after a meeting an update should run. Notify the assignee or configured email recipients.

Catch unfinished bookings

For form and click routers, notify your team when a prospect submits but doesn’t complete a booking.

Keep the context
moving with the meeting.

Send updates to the places your team already works. Combine supported actions in a workflow and review what happened when it ran.

Meeting eventsDistro workflowsEmail · Slack · Webhooks

Illustrative workflow · Meeting events connect to email, Slack, and webhook actions.

Email and Slack

Email the assigned rep or specific recipients, and post a message to a connected Slack channel.

Webhooks and visibility

Send meeting context to an external endpoint. Use action logs to inspect execution and investigate delivery issues.

FAQ

Frequently asked
questions

What can Distro workflows automate?

Workflows connect supported form and meeting events to notifications. Actions include Slack messages, email to the assigned rep or specific recipients, and webhooks.

Can I send an update before or after a meeting?

Yes. Before-meeting and after-meeting triggers let you set a time offset in minutes and choose the actions to run.

Can a workflow apply to only one router?

Yes. Choose the source type and limit the workflow to selected sources, such as a specific form router or booking link. Available triggers depend on the source type.

Can I test an action before enabling a workflow?

Yes. Preview the action output or send a test. Test emails go to the current user; Slack and webhook tests are identified as test deliveries.

Do workflows handle routing rules or create CRM records?

Routing rules and CRM record actions are configured separately in routers. Workflows handle notifications and webhook actions around supported events.

Do workflows support outbound meetings?

Meeting lifecycle triggers support outbound routers where outbound routing is enabled. Availability depends on your account setup.

Keep meetings moving.
Leave the updates to Distro.

Build a consistent follow-up process around the meetings your team books.

Explore scheduling