Integration Hub
WhatsApp, Telegram, Google Groups, Discord, Teams, Meta, Google Workspace, website forms, group sources, and import connectors with approval-safe write actions.
Outbound safety
Approval gated
Secrets
Server env only
Unofficial bridges
Read-only first
Real platform identity, groups, channels, sync telemetry, evidence, AI monitoring, and operator controls. Generic labels are replaced by API metadata or explicit reconnect diagnostics.
Connected
6/6
Sources
0
Messages
376
Evidence
151
Claims
21
Confidence
0%
Heartbeat
live
API
active
allien
connectedwhatsappreal metadata pending from platform API
Health
90%
Synced
0
AI
watching
0
0
0
0
0
0%
Telegram
connectedtelegramreal metadata pending from platform API
Health
90%
Synced
0
AI
watching
0
0
0
0
0
0%
Vendors Mailbox
connectedemailreal metadata pending from platform API
Health
90%
Synced
0
AI
watching
0
0
0
0
0
0%
Sales Mailbox
connectedemailreal metadata pending from platform API
Health
90%
Synced
0
AI
watching
0
0
0
0
0
0%
Support Mailbox
connectedemailreal metadata pending from platform API
Health
90%
Synced
0
AI
watching
0
0
0
0
0
0%
Admin Mailbox
connectedemailreal metadata pending from platform API
Health
90%
Synced
0
AI
watching
0
0
0
0
0
0%
Capabilities
Required env
Setup path
- Create Meta app
- Connect business phone number
- Configure webhook
- Add token to server env
- Run test inbound/outbound approval flow
Risks
- Template approvals required
- Outbound messaging must respect opt-ins
- Human approval required before sending
Capabilities
Required env
Setup path
- Run the private allien WhatsApp bridge
- Scan QR from the allien phone
- Protect session files
- Keep READ_ONLY=true for initial deployment
- Use ApprovalRequest before any send
Risks
- Unofficial; account risk
- Never expose bridge publicly
- Avoid bulk messaging
- Use official Cloud API later for production customer messaging
Capabilities
Required env
Setup path
- Create Telegram API app at my.telegram.org/apps
- Configure api_id/api_hash
- Login with phone OTP from Telegram app
- Keep READ_ONLY=true for research
- Use ApprovalRequest before any send
Risks
- User-session automation; rate-limit/account risk
- Do not scrape members without permission
- Never expose bridge publicly
- Outbound send requires approval
Capabilities
Required env
Setup path
- Add mailbox env vars server-side
- Run /api/integrations/email/status to verify IMAP/SMTP
- Run /api/integrations/email/sync to import INBOX
- Route every campaign/reply through AgentApproval before SMTP send
Risks
- Never expose mailbox passwords to the browser
- Keep EMAIL_ALLOW_APPROVED_SEND=false until approval UI is wired
- Bulk/campaign sends require explicit operator approval and rate limits
Capabilities
Required env
Setup path
- Create Meta app
- Connect page
- Request required permissions
- Configure webhook
- Verify review status
Risks
- Group access is restricted
- App review may be required
- Do not automate unsolicited DMs
Capabilities
Required env
Setup path
- Use Instagram Business account
- Link to Facebook page
- Request Graph permissions
- Configure webhook
Risks
- DM API availability depends on account/permissions
- No spam automation
Capabilities
Required env
Setup path
- Create Google Cloud OAuth client
- Enable APIs
- Authorize account
- Store tokens securely
- Verify scopes
Risks
- OAuth scopes must be minimal
- Drive sharing/deletion requires explicit confirmation
Capabilities
Required env
Setup path
- Enable Cloud Identity/Groups and Gmail APIs
- Authorize Google account with group scopes
- Select allowed client/vendor groups
- Sync conversations read-only
- Route replies through ApprovalRequest
Risks
- Workspace admin permissions may be required
- External groups may have limited API access
- Replies require explicit approval
Capabilities
Required env
Setup path
- Create Discord application + bot
- Invite bot to approved servers with least-privilege scopes
- Enable message content intent if required
- Store token server-side
- Keep outbound replies approval-gated
Risks
- Message Content Intent may require approval
- Only sync servers where user/admin installed the bot
- No unsolicited DM automation
Capabilities
Required env
Setup path
- Register Azure app
- Grant least-privilege Graph permissions
- Admin-consent required scopes
- Select allowed teams/channels
- Route outbound messages through ApprovalRequest
Risks
- Tenant admin consent usually required
- Graph chat message permissions are sensitive
- Outbound posts require approval
Capabilities
Required env
Setup path
- Create public forms
- Map fields to CRM
- Add spam/rate limits
- Route to Research Center
Risks
- Must add CAPTCHA/rate limiting before public launch
- Validate all inputs
Capabilities
Required env
Setup path
- Upload/import source
- Map columns
- Run dedupe
- Send to verification agent
Risks
- Respect platform ToS
- Do not scrape/private-message without permission