To authorize requests to the Blogs API, generate an API token with the required scope (e.g., emails/builder.readonly) and include it in your requests as a Bearer token. Your token grants access to endpoints such as emails/builder and blogs endpoints listed below.
In Trengo, configure the Blogs API connection by entering the API token and selecting the needed scopes. Test connectivity from the integration panel to ensure retries and success status.
– GET emails/builder – emails/builder.write – POST emails/builder – POST /emails/builder/data – DELETE /emails/builder/:locationId/:templateId – emails/schedule.readonly – GET emails/schedule – blogs/post.write – POST /blogs/posts – blogs/post-update.write – PUT /blogs/posts/:postId – blogs/check-slug.readonly – GET /blogs/posts/url-slug-exists – blogs/category.readonly – GET /blogs/categories – blogs/author.readonly – GET /blogs/authors
When a new blog post is published in Blogs API
Send an email notification to subscribers using the Email Builder, log the event in Trengo, and optionally create a CRM activity.
POST /blogs/posts
postId, title, slug, publishDate, authorId
When a new category or author is created in Blogs API
Update Trengo lists, create routing rules, and notify teams
GET /blogs/categories
categoryId, name, slug, description
When an email builder template changes in Blogs API
Sync templates into Trengo Email Builder, update existing campaigns, and trigger automation workflows
POST emails/builder
templateId, name, location, content
Fast, code-free automation for content-driven customer communications
Centralized content notifications across channels within Trengo
Scalable workflows that adapt as your blog grows
Key elements include endpoints, triggers, actions, fields, and data mappings used to automate your workflows between Blogs API and Trengo.
Application Programming Interface that lets apps talk to each other.
A specific URL and method that performs an action in an API.
A URL that gets called automatically when an event occurs, enabling real-time updates.
A blog entry published on your site; the data you retrieve or send may include title, slug, content, and publish date.
When a new post is published, automatically send a welcome email via the Email Builder to subscribers.
Post alerts appear in Trengo chats or tickets, enabling immediate team action.
Route posts to different teams based on category to tailor responses.
In Blogs API, generate an API token with the required scopes. Keep it secure.
Enter credentials in Trengo integration settings and test connectivity.
Map postId, title, slug, and other fields to Trengo data structures.
To access emails and blog data, you need the appropriate API token with the correct scopes (for example, emails/builder.readonly and blogs/*). Generate this token in the Blogs API admin area and grant it to your Trengo connection. Keep your token secure and avoid exposing it in client-side code. You may optionally add related scopes such as blogs/category.readonly or blogs/author.readonly to broaden access as needed.
No separate Zapier App Connector is strictly required. You can connect using standard API tokens and webhooks from Blogs API to Trengo. If you choose to use Zapier, you can map Blogs API actions to Trengo triggers, but the core connection still relies on a valid API token and proper field mapping. The integration can work with or without a dedicated Zapier App Connector.
Yes. Real-time updates are possible through webhooks or polling endpoints. Configure a webhook in Blogs API to notify Trengo when a new post is published, then route the data into Email Builder or chat workflows in Trengo. You can also periodically poll endpoints like GET /blogs/posts/url-slug-exists to verify content availability.
The endpoints most helpful for automation include GET /blogs/categories and GET /blogs/authors for metadata, POST /blogs/posts to publish content, and POST emails/builder or POST /emails/builder/data to trigger email notifications. These endpoints enable content-driven emails, routing, and content-aware notifications in Trengo.
Test the integration by generating a sample API token, connecting it in Trengo, and performing a dry run of a workflow. Validate that a new post triggers an email or chat notification and that data maps correctly (title, slug, postId). Use sandbox data when available and review logs in both Blogs API and Trengo for any errors.
Yes. This is designed to be no-code friendly. Use the Blog API’s endpoints for data access and Trengo’s Email Builder and workflow automations to set up triggers, actions, and field mappings without writing code. Webhooks further simplify real-time updates without custom development.
API keys and tokens are found in the Blogs API administration panel. Create or regenerate your API token with the required scopes, then securely store it in Trengo’s integration settings. Never share tokens publicly; rotate them periodically and monitor usage for any unusual activity.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
