Integration events
React to configured GitHub, HubSpot and other integration events.
Workflows
When this happens.The next step follows.
Connect events to actions with a visual workflow. Branch on conditions, loop over records, add an AI step and inspect what happened in every run.
Workflows
Start with the event that matters.
- Tasks, messages, mail and calendar events
- Table and Drive events
- Manual runs and schedules
Add a trigger
What starts this flow?
Workspace events
Task created
A new task is created in this channel
Message posted
Someone posts a message
Email received
A new email arrives in the channel inbox
Table row created
A row is added to a channel table
External & schedule
GitHub event
A webhook (push, PR, issue…) arrives
On a schedule
Recurring — every weekday at 09:00
Manual / Run now
Only when you run it by hand
13+ trigger types · webhooks · cronAdd trigger
Workflows
Make the logic visible.
- Branches, delays and loops
- Tasks, messages, email and table actions
- AI agent and HTTP request steps
Trigger
Task status changed
status → Blocked
Condition
If / branch
{{vars.urgency}} = high
Action
Send message
#oncall · {{trigger.title}}
Control
Wait / delay
1 day, then follow up
Add step
StepsAI agentFor eachHTTP request
Workflows
See what ran. Understand the result.
- Test runs
- Step-level inputs and outputs
- Execution history and errors
support-triage
Email received · active
Recent runs
● FailedJul 18, 09:12"HTTP request": 502 Bad Gateway
●Email receivedDone
●AI agentDone
output: { "urgency": "high", "topic": "billing" }●HTTP requestFailed
502 Bad Gateway — POST /tickets
Retry
● DoneJul 18, 08:00 Test run
● DoneJul 17, 16:45
● Waiting (delay)Jul 17, 09:00
01 / Triggers
Start with the event that matters.
Trigger a flow when a task changes, a message arrives, a document is added or a table row changes. You can also run it manually or on a schedule.
- Tasks, messages, mail and calendar events
- Table and Drive events
- Manual runs and schedules
Add a trigger
What starts this flow?
Workspace events
Task created
A new task is created in this channel
Message posted
Someone posts a message
Email received
A new email arrives in the channel inbox
Table row created
A row is added to a channel table
External & schedule
GitHub event
A webhook (push, PR, issue…) arrives
On a schedule
Recurring — every weekday at 09:00
Manual / Run now
Only when you run it by hand
13+ trigger types · webhooks · cronAdd trigger
02 / Visual builder
Make the logic visible.
Connect trigger, condition and action nodes on a canvas. Pass values between steps, wait when needed and repeat actions for each item in a collection.
- Branches, delays and loops
- Tasks, messages, email and table actions
- AI agent and HTTP request steps
Trigger
Task status changed
status → Blocked
Condition
If / branch
{{vars.urgency}} = high
Action
Send message
#oncall · {{trigger.title}}
Control
Wait / delay
1 day, then follow up
Add step
StepsAI agentFor eachHTTP request
03 / Run history
See what ran. Understand the result.
Test the workflow and inspect run history, step outputs and errors. Follow the path through a run before changing the next version.
- Test runs
- Step-level inputs and outputs
- Execution history and errors
support-triage
Email received · active
Recent runs
● FailedJul 18, 09:12"HTTP request": 502 Bad Gateway
●Email receivedDone
●AI agentDone
output: { "urgency": "high", "topic": "billing" }●HTTP requestFailed
502 Bad Gateway — POST /tickets
Retry
● DoneJul 18, 08:00 Test run
● DoneJul 17, 16:45
● Waiting (delay)Jul 17, 09:00
Workflows
More of what your day needs.
Secrets
Manage secrets for connections used in workflow steps.
Use context
Map values from the trigger and previous steps into actions.
Build with an assistant
Use the flow maker to help compose and revise a workflow.
A closer look.
Does every flow need AI?
No. Triggers, conditions and actions can run without an AI step. Add an agent only where the workflow needs it.
Can I inspect a failed run?
Yes. Run history and step details help you see outputs and errors.
Workflows
See it with your team in mind.
Let’s walk through the way your team could work in Polybase.