Email and messages

For: email an app sends because something happened: an order confirmation, a receipt, a notification to you.

Connects with: keys.

• API Key (starts re_): from Resend's API keys page.
• From Email: an address on a domain you have verified in Resend, like hello@yourshop.co.uk.

Ask for:

• "Email the client when a repair is done"
• "Send the buyer a confirmation when an order is placed"
• "Email me every time the contact form is used"

Limits: an app can send, and cannot reach your domains or API keys. Reading what was sent, or cancelling a scheduled email, is for your team only. The sender is always the From address you saved, and an app cannot choose another. Send only to an address the person typed, never one taken from the page's address. Resend bills your account, at their prices.

For: email an app sends, and sign-ups that join one of your Brevo contact lists.

Connects with: keys, from Brevo's API keys page.

• API Key (starts xkeysib-).
• From Email and From Name: the sender your mail shows.

Ask for:

• "Add a newsletter sign-up that adds people to my Brevo list"
• "Send a welcome email when someone signs up"

Limits: an app can send mail and add contacts, and cannot reach your account, senders or keys. Reading, updating and removing contacts is for your team only. The sender is fixed to the one you saved. Add only an address the person typed. Brevo bills your account.

For: email an app sends at scale: confirmations, receipts, notifications.

Connects with: keys, from Mailgun's API keys page.

• API Key (starts key-).
• Sending Domain, like mg.yourdomain.com.
• From Email.

Ask for:

• "Send a receipt by email when someone pays"
• "Email the team when a booking is made"

Limits: an app can only send a message. The sending domain and the sender are fixed to what you saved, because they decide whose reputation the mail is sent on. Mailgun bills your account.

For: a newsletter sign-up form on the site, and your subscribers on a team screen.

Connects with: keys.

• API key: in Mailchimp, Profile, then Extras, then API keys, then Create A Key. It ends in a data centre, like -us21.
• Audience ID: Audience, then All contacts, then Settings, then Audience name and defaults.

Ask for:

• "Add a newsletter sign-up to the footer that joins my Mailchimp audience"
• "Make a team page with my newest subscribers"

Switches: Read subscribers, Subscribe people, and Read the audience details.

Limits: every sign-up is sent as pending, so Mailchimp emails the person to confirm and the app says "Check your inbox". An address already on the list is told so. Sign-ups carry a tag, Website unless you ask for another. The app works with the one audience you chose. Anyone can sign up from the form, but reading subscribers is for your team only.

For: newsletter and SMS sign-ups, and events like an order placed or a form sent, which start your flows in Klaviyo.

Connects with: keys, from Klaviyo's API keys page.

• Private API key (starts pk_): choose Create Private API Key, then Custom key, with Full Access for Lists, Profiles, Subscriptions and Events. Subscribing needs write access to lists, not only read.
• Default list ID: optional. In Klaviyo, open the list, then Settings.

Ask for:

• "Add a newsletter sign-up to the home page"
• "Record an Order placed event in Klaviyo when someone pays"
• "Show my lists on the team page"

Switches: Read profiles, Add and change profiles, Subscribe people to lists, Read events, Add and change events, Read lists.

Limits: an app subscribes only an address the person typed, and the list's own double opt-in setting decides what Klaviyo sends. Visitors can sign up and record events. Reading lists and profiles is for your team only.

For: a newsletter subscribe form, and your latest posts shown on the site.

Connects with: keys.

• API key: in beehiiv, Settings, then Integrations, then API, then New API key.
• Publication ID (starts pub_): on the same API page, under your publication.

Ask for:

• "Add a beehiiv sign-up form to the home page"
• "Show my five latest beehiiv posts with a link to each"

Limits: the app is pinned to your one publication. It can subscribe an address the person typed, which sends your welcome email, and read your posts. Your list of subscribers cannot be reached from an app.

For: text messages: verification codes, order confirmations and alerts.

Connects with: keys, from the Twilio console.

• Account SID (starts AC) and Auth Token.
• From Phone Number, with the country code, like +447700900123.

Ask for:

• "Text the customer when their order ships"
• "Send a six digit code to the phone number on sign-in"

Limits: an app can send a text and nothing else, because the same credentials could buy phone numbers. The number a text comes from is fixed. Every text costs money and rings a real phone, so calls are limited tightly for each visitor. Twilio bills your account. Test connection reads your last message and sends nothing.

For: messages from your own business number: a confirmation, an order update, a reminder.

Connects with: two values, from Meta for Developers: open your app, then WhatsApp, then API setup.

• Permanent access token: a System User token that does not expire.
• Phone number ID: the ID shown under the number, not the number itself.

Ask for:

• "Send a WhatsApp confirmation to the customer after they book"
• "Send an approved template to someone who asked to be reminded"

Limits: a plain text works only within 24 hours of the person's last message to your business. To start a conversation you need an approved template. Until your Meta business is verified, messages reach only the test numbers added on the API setup page. Receiving replies is not included. Numbers are written as digits with the country code and no plus. Its page shows Billed by WhatsApp Business.

For: alerts and notifications to a Telegram chat, sent by a bot of your own. This is not the Setherion bot that changes your apps: for that, see Telegram.

Connects with: a Bot Token (looks like 123456:ABC-DEF...) from @BotFather, and a Default Chat ID, which is optional but needed for the app to know where to send.

Ask for:

• "Send me a Telegram message when someone fills in the contact form"
• "Post each new order to my Telegram group"

Limits: an app can send text, photos and documents, and nothing else. It sends only to the chat you configured. Test connection asks Telegram who the bot is and sends nothing.

For: alerts to a Slack channel: a sign-up, a form sent, an error.

Connects with: either way.

• Connect with Slack: sign in, allow the app, then press Choose channel. Apps post to the channel you chose.
• Incoming Webhook URL (starts https://hooks.slack.com/): create one at Slack's webhooks page. It belongs to one channel, so changing channel means making a new one.

Ask for:

• "Post to Slack when a new member signs up"
• "Send a Slack alert with the order number and total for every sale"

Limits: nothing reads your messages, files or direct messages. With the button the app can post to your chosen channel and list channels, and with a webhook it can only post. Test connection with a webhook posts a test message in the channel.

For: alerts to a Discord channel: a new order, a form sent, a booking made.

Connects with: either way.

• Connect with Discord: sign in, then choose the server and channel apps may post to.
• Bot token and Default channel ID: in the Discord Developer Portal, open your application, then Bot, then Reset Token. For the channel, turn on Developer Mode in Discord settings, then right-click the channel and choose Copy Channel ID.

Ask for:

• "Post to my Discord when a booking is made"
• "Send a card with the name, date and party size for each booking"

Limits: with a bot token, invite the bot to the server with permission to send messages in that channel, or Discord answers with an error. Messages are plain text up to 2000 characters. Through the button, mentions are switched off, so an @everyone in a post is only text. Nothing reads your messages.

For: push notifications on phones and computers. People turn them on with a button, choose topics like news or offers, and your team sends from a team screen.

Connects with: three values, from the Firebase console.

• Web app config: Project settings, then General, then Your apps, a Web app (add one if there is none). Paste the whole firebaseConfig block.
• Web Push key: Project settings, then Cloud Messaging, then Web Push certificates, then Generate key pair. Copy the long key that starts with B.
• Service account key: Project settings, then Service accounts, then Generate new private key. Paste all of the file. It never reaches an app. In Google Cloud IAM, give the firebase-adminsdk account the role Firebase Cloud Messaging API Admin, or devices cannot join topics.

Ask for:

• "Add a Turn on notifications button, and a team page to send a message to everyone"
• "Let people choose between news and offers notifications"

Switches: Send notifications, and Sign devices up to topics.

Limits: only your team can send. A visitor can turn notifications on and put their own device on a topic, never send one. On an iPhone, the app must be added to the Home Screen first. Notifications cannot be turned on in the editor's preview, only in the published app.

For: live updates that appear on other people's screens without a refresh, like a chat or a live counter.

Connects with: four values from the Pusher dashboard: App ID, Key, Secret and Cluster (like eu).

Ask for:

• "Add a live chat box to the page"
• "Show a new order on the staff screen as soon as it is placed"

Limits: the key and cluster are public by design and reach the published app so it can listen. The secret stays on Setherion's servers and signs what the app sends. Only public channels work, and anything sent is seen by everyone on that channel, so nothing private belongs in one. Pusher bills your account.

For: bookings in Outlook, your free and busy times, and mail your team sends from your Outlook address.

Connects with: the Connect with Microsoft button. You sign in and allow Setherion to make a calendar named "Setherion bookings", read when you are busy, and send mail your team writes. There are no keys.

Ask for:

• "Let visitors book a 30 minute call in my free times, and add it to my Outlook"
• "Make a team page with the bookings made"
• "Let my team reply to a customer from my Outlook address"

Switches: Read bookings, Add, move and cancel bookings, See when you are busy, and Send mail from your mailbox.

Limits: apps reach the "Setherion bookings" calendar and no other, and your own events are never read. Visitors see only when you are busy, never what. A booking invites nobody, so a visitor's details go into the booking itself. Reading the bookings and sending mail are for your team only. Mail goes only from a team screen, and only what the team wrote.