◆Block
Circleback Block
Trigger workflows from Circleback meeting completions and notes
The Circleback block is a trigger that starts a workflow when a Circleback AI meeting assistant event fires. Reach for it when you want to automate follow-ups from meetings — receiving notes, action items, transcripts, and recordings the moment a meeting completes.
Overview
| Property | Value |
|---|---|
| Type | circleback |
| Category | triggers |
| Color | #0097A7 |
When to Use
- Kick off a workflow automatically when a Circleback meeting completes
- Route meeting notes into a knowledge base or document store
- Turn extracted action items into tasks, tickets, or reminders
- Summarize or analyze meeting transcripts with a downstream Agent block
- Notify a team channel with the recording URL and attendees after each meeting
- Archive full meeting data for compliance or reporting
Configuration
This block is a trigger and has no configurable sub-blocks. It activates from incoming Circleback webhook events. The available trigger events are:
circleback_meeting_completed
Fires when a Circleback meeting finishes processing.
circleback_meeting_notes
Fires when meeting notes become available.
circleback_webhook
Generic Circleback webhook event.
Inputs & Outputs
- Inputs: none (this block is a trigger / workflow starter)
- Outputs:
id(number) — Meeting IDname(string) — Meeting nameurl(string) — Meeting URLcreatedAt(string) — Created at timestampduration(number) — Meeting duration in minutesrecordingUrl(string) — Recording URLattendees(json) — Meeting attendeesnotes(string) — Meeting notesactionItems(json) — Action itemstranscript(json) — Meeting transcriptmeeting(json) — Full meeting data
YAML Example
circleback_1:
type: circleback
name: "Circleback"
connections:
outgoing:
- target: agent_1