Start any workflow, from anything

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→
08:5909:00

morning_briefing

Cron·0 9 * * *

morning_briefing

Starts the workflow on a repeating schedule.

Inputs:

Schedule

0 9 * * *

Daily at 9:00

Completed · 1 result

Output:

Run IDrun_4821
Slack
Discord
LINE

deploy_on_mention

Webhook·POST /hooks/deploy

deploy_on_mention

Starts the workflow when an external service sends an HTTP request.

Inputs:

Method

POST

Path

/hooks/deploy
Completed · 1 result

Output:

Run IDrun_5307

Bridge Agent

Update Bridge MD parser and docs for nested sections

Running
SourceFrom Bridge MD Workflow
MCP Servers3 active
Steps5
8月27日

App events & schedules

A channel for chat, a clock for schedules

Post into your own tenant URL like a channel — or put the same job on a schedule.

POST/hooks/workflow

Run a .workflow.md

A chat message or CI event becomes the workflow's input.

POST/hooks/agent

Talk to an agent

The message lands in your agent's inbox — the result posts back.

POST/cron/jobs

Schedule it

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

slackdiscordopenai

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

Four ways to start

On a schedule

Cron syntax, or plain words like every morning at 9.

From an app event

A GitHub issue, a Slack mention — any HTTP POST to your URL.

HEARTBEAT.md

Schedules written in plain Markdown — the file is the config.

By hand

Hit run whenever you want it.

On your machineor in the cloudapprovals pause for a human

Stop checking. Start triggering.

Pick an event — Arg0 does the rest.