Integrations: outreach channels
In Integrations (/integrations) you connect your own messaging channels to send to leads from the Eryx app: email (Gmail or Microsoft 365), a Telegram bot, and WhatsApp Cloud API.
After a channel is connected, sending is available from the app (for example from a lead record) when allowed by your plan and workspace. Administrators set up any automated workflows on your organization’s side.
Credentials and tokens are stored encrypted on the server. If the UI shows a warning that connections are unavailable, contact support or your workspace administrator.
General requirements
- You must be signed in to Eryx.
- For email, after you click connect, your provider’s window opens; when you finish, you return to Integrations with a success or error message.
Gmail
Google Cloud Console setup (administrator, or you for your own Google Cloud project)
- Create or open a project in Google Cloud Console.
- Enable Gmail API if needed.
- Credentials → Create credentials → OAuth client ID → Web application.
- Under Authorized redirect URIs, enter the URI your Eryx deployment administrator gave you (usually your API URL with a path like
.../integrations/google-mail/callback). - Copy Client ID and Client Secret into your Eryx environment settings (your deployment administrator does this).
What access the app requests
Connecting only requests permission to send email (not full mailbox access). Long-lived access may be requested so sending works without signing in again.
Steps in Eryx
- Open Integrations.
- Click Connect Gmail.
- Sign in to the Google account and approve access.
- After success, you’ll see confirmation in the app.
Typically one Gmail connection is allowed per Eryx account; connecting again updates it.
If something goes wrong
After an error, the page URL may include an error parameter. Common cases:
| Value | What to do |
|---|---|
oauth_state | Start the connection again from Integrations. |
oauth_code | Sign in again with the provider or try later. |
no_encryption_key, not_configured | Contact your administrator or support — server-side configuration is incomplete. |
token_exchange | Check that the redirect URI in Google’s console matches what is configured for your environment. |
no_refresh_token | In your Google account settings, revoke access for the Eryx app and connect Gmail again. |
encrypt, db | Contact support. |
Microsoft 365 / Outlook
Azure (Entra ID) setup
- Azure Portal → Microsoft Entra ID → App registrations → New registration.
- Add a Web redirect URI — your Eryx administrator provides the value (typically
.../integrations/microsoft-mail/callback). - Create a Client secret; give the application ID and secret to the administrator for Worker configuration.
- Under API permissions, add delegated Microsoft Graph permissions for sending mail (Mail.Send) and, if needed, offline_access to refresh the token.
In Eryx
Integrations → Connect Microsoft → sign in and consent. URL error messages are similar in meaning to the Gmail table above.
Telegram bot
Getting a token
- In Telegram, open @BotFather.
- Run
/newbotand follow the prompts; BotFather will give you a token like123456789:AAH....
Connecting in the app
- Integrations → Telegram bot section.
- Paste the token into Bot token → Save connection.
The server validates the token with Telegram; if it’s invalid, saving will fail.
Important for delivery
Telegram cannot start a chat using only @username — you need a numeric chat ID. The contact must message the bot first (or tap Start); then you can save that ID on the lead in Eryx (Telegram chat ID field on the lead or outreach settings).
If the chat ID is missing, automated sending may fail with a prompt to fill it in.
WhatsApp Cloud API
What to enter in the UI
- Meta access token — Graph API access token for sending from your WhatsApp Business account (see current steps in Meta for Developers → your app → WhatsApp).
- Phone number ID — your WhatsApp Business phone number ID in the developer console.
Optional Template settings:
- Template name and Template language — if you need to send a Meta-approved template instead of free-form text.
When templates are required
Outside the 24-hour customer reply window, Meta usually requires an approved template. Set the template name and language when saving the connection if that applies to you.
Recipient number
The lead record should include a WhatsApp number in a format the app recognizes (often filled from contacts or enrichment). If unsure, check the lead’s contact fields.
Extra technical connection fields (API version, etc.) can be set by an administrator via internal tools — the standard Integrations form only needs the token, phone number ID, and template settings if applicable.
Managing connections
In Integrations you can add, view, and remove connections. There is usually one active configuration per channel type per account; saving again updates it.
If both Gmail and Microsoft are connected, the app picks the email channel according to product rules when you send from the UI (ask support if you need details).
Support
Extended technical documentation for teams that deploy and operate Eryx (API, automations, environment variables) is not published in the public docs. Request it from your administrator or support.
Product questions: business@eryx.digital or Help in the app after you sign in.