Automations
Automations are for teams that need more than one built-in connector. They allow post-meeting rules that decide where summaries, recordings, notes, or extracted tasks should go next.
Use automations when the meeting output must drive a downstream operational system instead of stopping at recap.
Wireframes
Section titled “Wireframes”┌──────────────────────────────────────────────────────────────────────┐
│ Hyper app.hyper.video/automations/new │
├──────────────────────────────────────────────────────────────────────┤
│ │
│ Automation builder │
│ │
│ Trigger: Meeting summary approved │
│ Filter: Weekly sync + workspace Product │
│ │
│ Actions │
│ ┌──────────────────────────────────────────────────────────────┐ │
│ │ 1. Post summary to Slack #team-sync │ │
│ │ 2. Create Notion page in Meeting Recaps │ │
│ │ 3. Assign unresolved tasks to project owners │ │
│ └──────────────────────────────────────────────────────────────┘ │
│ │
│ Safety │
│ - Skip confidential meetings │
│ - Require owner approval before external sharing │
│ │
└──────────────────────────────────────────────────────────────────────┘
The automation surface combines triggers, filters, and destinations so teams can route recap output intentionally.
When to use this
- You need routing by meeting type, attendee set, customer, project, or content pattern.
- Built-in integrations are not enough for the systems your team depends on.
Before you start
- Define the trigger conditions and target systems before opening the builder.
- Decide what should happen when a rule matches partially or a downstream destination is unavailable.
- Document ownership for automation changes because recap routing can affect many teams at once.
Settings and options
Automation design
- Start with one meeting type and one destination before building broad branching logic.
- Use review or draft modes for sensitive recap workflows until the team trusts the rule.
- Prefer explicit routing conditions over vague keyword matching when the downstream action is high impact.
What this feature helps with
Recipe builder
Create if-this-then-that automations with a visual builder. Trigger actions based on meeting type, participants, keywords, or calendar.
Webhook support
Send meeting data to any tool via webhooks. Integrate with Zapier, Make, or your own internal tools.
Task creation
Automatically create tasks in Linear, Jira, Asana, or other trackers from meeting action items. Assigned and due dates included.
How to work with it
Create a recipe
- Choose a trigger: meeting ends, action items created, or keywords detected
- Set conditions: meeting type, calendar, participants
Choose actions
- Send data to Slack, Notion, Linear, or any webhook
- Map meeting data to the fields your tool expects
Automations run after every meeting
- Matching meetings trigger the recipe automatically
- View logs to see what was sent and when
Where it fits well
Engineering teams
- Action items auto-create Linear or Jira tickets
- Sprint meeting summaries posted to #engineering
- Bug discussions tagged and tracked
- No manual ticket creation after meetings
Sales teams
- Client call summaries auto-sent to CRM
- Follow-up tasks created in Salesforce
- Deal-related meetings tagged by account
- Pipeline updates without manual entry
Operations
- Custom workflows for different meeting types
- Webhook integration with internal tools
- Audit trail of all automated actions
- Reduce manual post-meeting admin
What to expect
- Visual recipe builder
- Webhook support
- Task tracker integration
- Conditional triggers
- Meeting data mapping
- Execution logs
Questions that come up often
What tools can I connect?
Hyper has native integrations with Slack, Notion, Linear, Jira, and Asana. For any other tool, use webhooks or connect through Zapier/Make.
Can I create multiple recipes?
Yes. Create as many recipes as you need. Each can have different triggers, conditions, and actions.
How do I troubleshoot automations?
Every recipe has an execution log showing what triggered, what data was sent, and whether it succeeded. Use this to debug issues.
Related tasks
Limitations and rollout notes
- This workflow is documented as forward-looking and may not be available in every workspace yet.
- Downstream reliability depends on the destination tool and the chosen trigger conditions.
Troubleshooting
A rule fired unexpectedly
- Review the exact trigger conditions and the meeting metadata that matched them.
- Tighten the rule to one meeting class or project until the behavior is predictable.
- Add a manual review step for high-risk routes.