Channels, webhooks and schedules

Channels let people talk to the agent; webhooks let software trigger it; cron runs scheduled workspace commands. Choose the intended identity, conversation and permissions before connecting an automation.

Telegram: your personal agent

• Create a bot with Telegram BotFather using /newbot. Keep its token private.
• Open Settings → Channels → Telegram, enter Bot token and Save token. The agent can instead request it through the secure credential form.
• Immediately send /start from the intended Telegram account. The first chat is linked; other chats are refused. Verify Linked in Settings.
• Send a test message or attachment. Unlink chat allows another chat to be linked; replacing the token requires linking again. In shared mode each member has their own bot.

Slack: one deployment connection

Use a Slack app with Socket Mode, direct-message events and the required bot scopes. Connect its bot token and app-level token in Settings → Channels → Slack. The first user to direct-message the bot claims it; do this from the intended owner account. In shared mode only a global admin configures this deployment-wide bot.

Webex: a group’s shared agent

A group administrator opens Admin → Shared agent, selects the group and configures its agent. In Webex integration enter that group’s bot token. Set separate sender lists for querying knowledge, modifying knowledge and triggering tools, then Save Webex. A wildcard allows everyone in the space that capability; use explicit identities where appropriate.

Add the bot to a test space. Mention it in a group space; direct messages need no mention. Verify a permitted request and a refused action using a member identity. Each space has its own conversation; Room and Webex share the group agent settings. Disconnect clears the group token.

Channel execution

These connections are outbound and do not require a public Prism URL. Tool calls run automatically, without dashboard approval. Add credentials through secure web Settings before a task needs them. Channel turns may run up to one hour; expiry is reported explicitly.

Webhooks: receive an event

In Settings → Webhooks create a name and prompt, optionally select a conversation and model. {{content}} inserts the payload; without it, the payload is appended. Each hook has its own conversation by default. Copy its generated URL and token exactly. The prompt can tell the agent where to save or deliver the result.

curl -X POST "YOUR_GENERATED_WEBHOOK_URL" \
  -H "Content-Type: application/json" \
  -d '{"alert":"test","message":"Documentation check"}'

Use the full generated URL including its token, or send the token as X-Prism-Token or Authorization: Bearer. Default execution acknowledges immediately while the agent works; Wait for the agent needs a caller with a sufficient timeout. Pause disables the hook without deleting it, edits preserve URL/token, and deletion invalidates it. Anyone holding the token can trigger your agent; keep it out of public logs and screenshots.

Cron: data refresh or agent trigger

The cron tool schedules a workspace command. A data-refresh script can run without an AI request; an agent-triggering command can produce a report and deliver it to a linked channel. Specify timing, timezone, description and destination, then inspect the job in Tasks → Scheduled.

Set your profile timezone before creation. Existing jobs keep their timezone after a profile change. enable/disable pauses and resumes; update edits in place; remove stops future runs. Link dashboard-specific jobs to widgets so cleanup can track their dependencies.