Integrations

Settings → Integrations. Owners and admins only.

Two kinds, and it helps to know which is which:

• In the right panel. Stripe. Pulls the customer’s account into ShareMail, so you see who you are talking to without opening another tab.
• Out to chat. Slack and Discord. Pushes inbox events out to the channel your team already watches, so nobody has to keep ShareMail open to know something needs them. One direction only: ShareMail posts, nothing comes back, and nothing in the channel is read.

Every key is encrypted at rest and read only to make the call. The settings screen shows whether a key is set, never what it is.

Stripe: billing beside the email

Connect a Stripe key and the right-hand panel gains a Stripe button, beside Contact details. Open a conversation and you see that customer’s plan, seat value, renewal or trial end date, last invoice, and whether they owe you money, matched on their email address. Teammates see it on their next page load.

Where to find the key

1. Open the API keys page in your Stripe Dashboard: Developers, then API keys (or go straight to dashboard.stripe.com/apikeys). Stay in live mode unless you want test customers.
2. Click Create restricted key. When Stripe asks how you will use the key, choose Providing this key to a third-party application. ShareMail is a separate app reading your Stripe data, which is what that option means.
3. Name: ShareMail. URL: https://sharemail.app. Tick Customize permissions for this key; left unticked, Stripe picks a broader default set.
4. Stripe pre-fills a long list with many Write permissions (Charges, Payment Intents, Payouts, Products, most of Billing). Clear it first: click None on every bold group header (Core, Billing, Connect and the rest). Then type customers, subscriptions and invoices into Filter resources and set each of those three to Read. Leave the Connect permissions column on None. Click Create restricted key.
5. Complete Stripe’s two-factor prompt, then copy the key. It starts with rk_live_ and Stripe shows it only once.
6. Paste it into ShareMail and click Connect.

A restricted key is all this needs. A full secret key (sk_live_) works too, but it can do anything in your Stripe account, so use one only if you have a reason to.

Check it works

Click Check the key on the Stripe card. ShareMail asks Stripe about an email address nobody has: a working key answers “no such customer”, which is a pass. A key that is expired, or that lacks read access to Customers, is reported with the reason.

Test-mode customers are labelled and link to the test dashboard, so test data never reads as production.

Slack and Discord: notifications out

Paste an incoming webhook URL and ShareMail posts into that channel. A webhook is a secret URL that accepts messages for one channel: anyone holding it can post there, so treat it like a password.

Three events, each switchable on the card:

• @mentions (on by default): a teammate typed @you in an internal comment.
• Assignments (on by default): a conversation was assigned to someone.
• New conversation nobody owns (off by default): a new conversation arrived in a shared inbox and nobody has picked it up. It is the busiest of the three, and the one that turns a channel into noise on a busy desk.

Subject lines only. Message bodies and comment text never leave the inbox: a chat channel usually has a wider audience than the inbox does.

Personal inboxes never post. Only shared inboxes reach a channel.

Where to find a Slack webhook URL

1. Open api.slack.com/apps and click Create New App, then From scratch. Name it ShareMail and pick your workspace.
2. In the app’s menu choose Incoming Webhooks and switch Activate Incoming Webhooks on.
3. Click Add New Webhook to Workspace, choose the channel the posts should land in, and Allow.
4. Copy the Webhook URL. It starts with https://hooks.slack.com/services/.

Where to find a Discord webhook URL

1. In Discord, open your server’s settings: click the server name at the top left, then Server Settings. You need the Manage Webhooks permission on that server.
2. Choose Integrations, then Webhooks, then New Webhook.
3. Give it a name (ShareMail) and pick the channel the posts should land in.
4. Click Copy Webhook URL. It starts with https://discord.com/api/webhooks/.

A link to the channel itself (discord.com/channels/...) is not a webhook, and ShareMail will say so if you paste one.

Check it works

Click Send a test message on the card. A short hello lands in the channel within a second or two. If the webhook was deleted on the other side, ShareMail tells you, and the fix is to remove the key here and create a new webhook.

Turning one off

Switching an integration Off keeps the key so you can switch it back on. Remove key forgets it entirely, and you will need a new one from the other service.