Create a channel
create_channelCreate a channel on an agent or an app. On an agent: a cron or heartbeat channel that wakes it on a schedule, a webhook channel that lets callers outside Valet reach it, or an mcp channel that serves it as an MCP server; what the agent does when it fires is the prompt file channels/.md in its source. On an app: a webhook, cron, or heartbeat channel whose deliveries Valet posts to path in the app, which only an app channel takes, so a private app takes webhooks and scheduled work without becoming public. Valet checks a webhook's signature before anything reaches the app, then posts the request as the sender sent it; a cron or heartbeat fire posts a small JSON body. Each delivery carries an X-Valet-Visitor token of kind channel and a delivery_key to treat as an idempotency key; return 2xx, and anything else retries for about a day. A webhook is signed by a secret held as an environment variable of the agent or app, and this never takes or returns a secret value: name it first in set_env_vars secret_names, whose request page the person opens to enter it, then pass its name as secret_name. A webhook without secret_name is refused. Creating a channel that already exists with the same kind and settings reports it and changes nothing; different settings are refused, so destroy it first. Slack and Telegram need a browser, so for them this gives the step to take and creates nothing. Otherwise it returns the channel's name and kind, its url, schedule, next fire time, secret_name, and prompt_path where they apply, and already when it existed. Requires connecting a Valet account.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"name": "<name>",
"channel": "<channel>",
"channel_kind": "<channel_kind>"
},
"name": "create_channel"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | The agent's or app's name, as list_services shows it. It is the one that will hold the channel. | |
| path | No | Where in the app Valet posts each delivery, such as /webhooks/stripe, so the app routes the channel's traffic to the handler that serves it. | |
| channel | Yes | What to call the channel, such as stripe-events, so later calls can attach, reauthorize, or destroy it by name. On an agent it also names the prompt file channels/<name>.md that says what to do when the channel fires. | |
| org_name | No | The Valet organization the agent or app belongs to. Omit to use the organization the account joined first. | |
| schedule | No | For cron, a schedule such as 'weekdays at 9:00am' or 'every 30 minutes' or a five-field cron expression. For heartbeat, an interval such as '15m', from 30s to 24h. Not used by other kinds. | |
| timezone | No | For cron, the place whose local time the schedule follows, as an IANA timezone such as America/New_York, so a 9:00 schedule fires at 9:00 there through daylight saving changes. Omit to read the schedule in UTC. | |
| secret_name | No | Needed for webhook. The name of an environment variable on this agent or app that holds the signing secret, named first in set_env_vars secret_names so the person enters it. Not used by other kinds. | |
| channel_kind | Yes | The kind of channel: cron, heartbeat, webhook, mcp, slack, or telegram, as list_catalog_channels lists them. An app takes webhook, cron, or heartbeat only. Slack and Telegram give the step to take instead of creating anything. | |
| verify_scheme | No | For webhook, how the sender signs: hmac-sha256 (the default), static-token for a sender that cannot sign, stripe, svix, slack, or mercury. This tool creates signed webhooks only, so there is no way to turn verification off. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||