How integrations work
Every external service Brixit talks to is connected with credentials you create in your account with that provider. You paste them into Settings → Integration keys, and from then on you can connect, change or rotate an integration yourself without anyone needing access to the server.
Why your own keys
A shared set of keys would mean your ad spend, your enquiries and your mailboxes all flowing through an account somebody else controls. With your own credentials, the provider sees your business as the client it is, rate limits are yours alone, and revoking access is something you can do from your own dashboard.
What is stored, and how
Anything marked as a secret is encrypted before it is written to your database and is never shown again — the field displays Saved — type to replace. To change a secret, type the new value over it. To keep what is there, leave the box empty.
Non-secret values such as an App ID or a Site Key are stored as-is, because they are public by design and appear in the page source anyway.
The page
Credentials are grouped by what they do:
- Lead sources — Meta, Google and TikTok ads
- Email — outbound delivery, and inbox sync
- Realtime — in-app messaging
- Mobile — push notifications
- Security — bot protection
- Product features — maps and enrichment
Each platform shows Ready to connect once everything required is saved, and Needs credentials until then. Test credentials asks the provider whether they are valid, which is worth doing before you rely on an integration.
Redirect URIs
Some providers require you to register a redirect URI — the address they send the browser back to after authorising. Brixit shows the exact value on each platform’s card. Copy it and register it verbatim; an extra slash or a http where the provider expects https is enough to make authorisation fail with an unhelpful error.