Automations

Automations send conversation data to the people and systems that need it. Use them when a completed conversation should notify your team, update a CRM, send a participant follow-up, or produce a recurring digest.

Automations live on the Perspective's Design page. Open the right-side panel, switch to Settings, and expand Automations. You can also ask the design agent to create or update them in natural language.

Automation Types#

Per Interview#

Per-interview automations run after each conversation reaches a terminal state. Use them for:

• Team notifications when a participant finishes or a conversation is reviewed
• Webhooks to your backend, Zapier, Make, or a data warehouse
• Slack updates in research or support channels
• HubSpot form or contact updates
• Participant follow-up emails

Built-in settings also live here:

• Interview summaries: team summary emails when conversations complete.
• Thank-you email: optional built-in thank-you email to participants.

If you create a custom participant email automation, the built-in thank-you toggle is hidden while that automation is enabled so participants do not receive duplicate follow-up emails.

Scheduled#

Scheduled automations send recurring daily or weekly digests. Use them when the team needs a regular summary instead of one notification per conversation.

Channels#

Perspective supports these automation channels:

Slack, HubSpot, and Gmail-backed participant emails require the matching workspace integration to be connected before delivery can work.

What Data Automations Receive#

Automation payloads can include:

• Conversation status and IDs
• Summary and trust assessment when available
• Transcript-derived structured output from Form Fields
• Participant metadata from URL Parameters, invite context, embeds, or connected channels
• Tags and other workflow context when available

For exact webhook payload fields, see Webhooks. For implementation patterns, see Automation Recipes.

Conditions#

Use conditions when only some conversations should trigger an automation. Common filters include tags and trust score ranges. For example, you can send low-trust conversations to a review channel or only sync qualified leads.

Testing and Monitoring#

After creating an automation:

1. Run a test delivery when possible.
2. Complete a normal participant conversation that should trigger it, or use an automation test delivery when available.
3. Open the completed conversation and check the Activity tab for delivery status.
4. If a delivery fails, open the automation in Settings to review or update the configuration.

Perspective tracks delivery status for customer-facing automation steps so you can see whether messages, webhooks, redirects, and CRM submissions completed, failed, or were skipped. Preview conversations are for testing conversation behavior and should not be used as the source of truth for production automation delivery.

How Automations Relate to Completion Flows#

Use Completion Flows when the participant should be redirected to a next step at the end of the conversation.

Use automations when data needs to move server-side after the conversation completes, such as posting to a webhook, updating HubSpot, sending a Slack message, or emailing the participant.