Run tasks on a schedule, kick off work when something happens in your apps, or chain Bridge MD workflows together. Any trigger can invoke any workflow — your AI assistant handles the rest.
Triggers→morning_briefing
morning_briefing
Starts the workflow on a repeating schedule.
Inputs:
Schedule
Daily at 9:00
Output:
deploy_on_mention
deploy_on_mention
Starts the workflow when an external service sends an HTTP request.
Inputs:
Method
POSTPath
Output:
Bridge Agent
Update Bridge MD parser and docs for nested sections
App events & schedules
Post into your own tenant URL like a channel — or put the same job on a schedule.
POST/hooks/workflow
A chat message or CI event becomes the workflow's input.
POST/hooks/agent
The message lands in your agent's inbox — the result posts back.
POST/cron/jobs
Register a real expression — 0 9 * * * — and it fires on schedule.
e.g. — a channel or a clock, same work
A channel people post into
you.arg0.app/hooks/workflow
your tenant domain · your secret
deploy.workflow.md
runs the file
the result posts back to the same channel
A clock that fires it
0 9 * * *
you.arg0.app/cron/jobs
your tenant domain · registered once
digest.workflow.md
fires on time
every morning, hands-free — local or cloud
the .workflow.md declares its own triggers
one tenant domain per account — never a shared inbox
deploy.workflow.md
--- trigger: webhook: /hooks/deploy cron: 0 9 * * * ---
Trigger types
Cron syntax, or plain words like every morning at 9.
A GitHub issue, a Slack mention — any HTTP POST to your URL.
Schedules written in plain Markdown — the file is the config.
Hit run whenever you want it.
Pick an event — Arg0 does the rest.