Use an API key with the Blogs API scope emails/builder.readonly to securely fetch blog content and post data. Store credentials securely and rotate keys regularly.
Grant TrustPulse access to your Blogs API using OAuth or a dedicated API key so TrustPulse can read blog data, create emails, and trigger campaigns.
Blogs API endpoints include: POST /blogs/posts, PUT /blogs/posts/:postId, GET /blogs/posts/url-slug-exists, GET /blogs/categories, GET /blogs/authors. Email builder endpoints include: GET emails/builder, POST emails/builder, POST /emails/builder/data. Scheduling endpoints: GET emails/schedule. This page focuses on the intersection that powers TrustPulse connections.
Trigger: A new blog post is published in Blogs API.
Actions: Create or update a TrustPulse email draft, queue a campaign, or trigger automated follow‑ups.
POST /blogs/posts
title, slug, excerpt, content, categoryId, authorId
Trigger: Blog post updated in Blogs API
Actions: Update TrustPulse campaign content, re-segment audiences, or refresh email templates.
PUT /blogs/posts/:postId
postId, title, slug, content, updatedAt
Trigger: Check slug existence via Blogs API
Actions: Create or map slug fields in TrustPulse to ensure clean, unique URLs
GET /blogs/posts/url-slug-exists
slug
Build powerful integrations without writing a line of code.
Automate cross‑platform workflows between Blogs API and TrustPulse using triggers and actions.
Easily maintain data consistency and reduce manual data entry.
This glossary explains core terms you’ll encounter: endpoints, triggers, actions, and data fields used when connecting Blogs API with TrustPulse.
A specific URL path provided by an API used to perform a function.
An event that starts an automation in TrustPulse when something happens in Blogs API.
A URL-friendly version of a post title used in links.
A sequence of marketing messages designed to engage an audience.
Automatically send a welcome email when a new blog post is published.
Suggest related posts to readers based on the post slug and category data.
Send targeted newsletters to readers by blog category to boost engagement.
Connect your Blogs API and TrustPulse accounts by granting permissions and selecting the required scopes.
Configure which blog events will trigger messages and map the data fields into TrustPulse.
Run end-to-end tests to ensure reliable delivery and monitor results after going live.
The Blogs API integration connects your blog data to TrustPulse so you can trigger emails and campaigns based on new or updated posts. No code is required for standard automations, and you can map fields like title, slug, and category to drive campaigns.
No coding is required to enable the basic flow. If you need advanced logic, you can enhance the workflow with conditional splits or by combining with Zapier for custom routing.
For a basic setup, you’ll use endpoints like POST /blogs/posts, PUT /blogs/posts/:postId, GET /blogs/posts/url-slug-exists, GET /blogs/categories, and GET /blogs/authors. These endpoints let you create, update, and validate posts, categories, and author data as part of your campaigns.
Yes. You can sync categories and authors to TrustPulse and use that data to segment campaigns. This helps tailor emails by topic and author.
Slug conflicts can occur if two posts share the same slug. Use the slug exists endpoint to validate uniqueness, generate a new slug, and map it in TrustPulse to avoid duplicates.
Yes, you can test triggers using sample data or a draft post. Use test environments and logs to verify delivery before going live.
Results and logs can be viewed in TrustPulse workflow dashboards and in the Blogs API response logs if available. Use error details and delivery stats to optimize campaigns.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
