Integrating Trengo
Auth: OAuth 2.0 · Partner program: not required · Setup time: about 20 minutes · Last verified: 2026-05-23
Trengo is a multichannel inbox covering WhatsApp, email, SMS, chat, and voice. The adapter targets the Trengo REST API and surfaces tickets, contacts, channels, and teammates into the canonical customer-support schema.
Auth model
Section titled “Auth model”- OAuth 2.0 Authorization Code grant for multi-tenant apps, or a Personal Access Token for single-account installs.
- Bearer token sent as
Authorization: Bearer <token>on every request. - The OAuth
authorizeandtokenURLs are surfaced through the Trengo developer portal once an app is registered; they are not published as a global pair. Copy them into the adapter’sauthUrl/tokenUrlsettings during configuration.
Prerequisites
Section titled “Prerequisites”- A Trengo workspace at trengo.com.
- For OAuth: a registered app via the Trengo developer portal (developers.trengo.com) with a redirect URI configured.
- For single-tenant deploys: a personal access token from Settings → Apps & Integrations → REST API.
Configure in admin
Section titled “Configure in admin”- Open
/platformsin the admin UI, filter to Customer Support, click Trengo. - Fill Configure:
- For OAuth:
clientId,clientSecret, andredirectUri(${PUBLIC_BASE_URL}/auth/customer-support/trengo/callback). - For token mode: paste the personal access token as
apiKey.
- For OAuth:
- Enable the adapter.
Required scopes
Section titled “Required scopes”Trengo’s scope catalog is exposed in the developer portal at app-registration time. Request the minimum needed for the canonical surface: ticket read/write, contact read/write, channel read, team read.
Webhooks
Section titled “Webhooks”Configure under Settings → Webhooks. Trengo lets you set a shared secret per webhook; deliveries are signed with HMAC-SHA256 in the X-Trengo-Signature header. The adapter verifies signatures against the raw body.
Subscribe to ticket.* and message.* events for full conversation coverage.
Quirks worth knowing
Section titled “Quirks worth knowing”- 120 requests / minute account-wide. The adapter back-pressures; bulk imports should be chunked.
- Channels are first-class. Conversations are scoped to a specific channel (WhatsApp number, mailbox, etc.) — when creating outbound, the channel id is required.
- WhatsApp message-template gating. Outbound WhatsApp outside the 24-hour session window requires a pre-approved template id; the adapter does not auto-approve templates.
References
Section titled “References”opensteward.dev ·Plans and free license ·Terms ·Privacy ·support@opensteward.dev
© 2026 Falco Consulting AB. Built from open-steward/opensteward@a3961d8. This site sets no cookies, runs no analytics and loads nothing from other sites, except platform logos from Brandfetch on the Platforms page.