Automations
Integrations
Steps that talk to other services use a connection: the key or sign-in for that service, saved once per app. Add them under Build → Automations → Connections. Secrets are stored encrypted and are never shown again, not even to you; to change one, connect again. This list is generated from appTown itself.
| Connection | How to connect | You enter | Used by |
|---|---|---|---|
| Slack | In Slack, add an Incoming Webhook to a channel and paste its URL. | Webhook URL | Post to Slack |
| Discord | In a Discord channel's settings → Integrations → Webhooks, copy the webhook URL. | Webhook URL | Post to Discord |
| Microsoft Teams | Add an Incoming Webhook (or a Workflows webhook) to a Teams channel and paste its URL. | Webhook URL | Post to Microsoft Teams |
| Telegram | Create a bot with @BotFather and paste its token; the step names the chat ID. | Bot token | Send a Telegram message |
| Google (Sheets, Calendar) | Sign in with the Google account whose sheets and calendars the automations use. | a sign-in (no key to copy) | Add a row to Google Sheets; Create a Google Calendar event |
| MCP server | The URL of an MCP server (Streamable HTTP) and, if it needs one, a bearer token. | Server URL, Bearer token (optional) | Call an MCP tool |
| REST API key | A key for an API you call with "Call a REST API": it is sent in the header you name, never shown in logs. | Header (e.g. Authorization), Value (e.g. Bearer sk_…) | Call a REST API (any URL) |
#Slack, Discord and Microsoft Teams
Each uses an incoming webhook URL from that service: create one for the channel the
messages should go to, and paste it. The step's message is a template:
New job for {{[Customer].[Name]}}: {{[Title]}}.
#Telegram
Create a bot with @BotFather and paste its token. The step names the chat ID to send to (a person or group that has started a chat with the bot).
#Google Sheets and Google Calendar
Sign in with the Google account whose sheets and calendars the automations should use.
- Add a row to Google Sheets: the spreadsheet's ID (from its address) and what goes in the row.
- Create a Google Calendar event: the calendar's ID and the event's title and details.
#MCP servers
An MCP server's URL (Streamable HTTP) and, if it needs
one, a bearer token. The Call an MCP tool step names the tool, sends its arguments as a
JSON object (with {{ }} for record values), and can save the answer in a field.
#REST API keys
For Call a REST API: the header to send (like Authorization) and its value (like
Bearer sk_…). The value is added to the request and is never shown in the run log.
#Your apps from outside
To go the other way (other systems reading and changing appTown records), see Developers.