Documentation

Integrations

Connect monitors, CI and other services, and automate the busywork with Lua.

  • Incoming webhooksLet monitors, CI and other tools post into a channel, in the format Slack webhooks use.
  • Outgoing webhooksSend people's messages from a channel to another service, and post its answers back.
  • Bots and the chat APILet scripts and other programs post and read public channels as a bot, with tokens that reach only what you allow.

Automations

Small Lua scripts that react to messages, run on schedules, answer commands and webhooks, and call other services.

  • Your first automationFrom an empty editor to a script that answers in your chat, step by step.
  • The editorCompletions, the linter and formatter, test runs, the webhook URL, run logs and history: everything the automation editor does.
  • Events, schedules, commands and webhooksEverything an automation can react to: what happens in channels, button clicks, schedules, slash commands and requests to its webhook URL.
  • Data, secrets, HTTP and librariesKeep data between runs, keep API tokens out of scripts, call other services, and share code between automations.
  • ExamplesComplete automations to copy: welcomes, standups, approvals, webhooks from GitHub, uptime checks, kudos, a weekly digest and more.
  • Sharing automationsExport automations with the libraries they need, and import them on another server after a preview.
  • AI and MCPLet an AI model write automations in the editor, or connect your own agent through MCP.
  • Automation storeBrowse automations other people publish, and install one with a click after a preview.
  • Limits and safetyWhat the sandbox allows, how much a script may do, and what keeps automations from harming the server.
  • API referenceEvery sideporch function automations can call, and the tables their handlers receive.