To use Blogs API with Dubb, authenticate requests with a valid access token that includes the emails/builder.readonly scope. Keep tokens secure and refresh before expiry.
Dubb authenticates with the GHL integration using OAuth 2.0 tokens. Obtain an access token via client credentials and attach it to each request.
Key endpoints include: GET emails/builder, POST emails/builder, POST /emails/builder/data, DELETE /emails/builder/:locationId/:templateId, GET emails/schedule, GET /blogs/posts/url-slug-exists, POST /blogs/posts, PUT /blogs/posts/:postId, POST /blogs/post-update.write, GET /blogs/categories, GET /blogs/authors, GET /blogs/categories, GET /blogs/authors.
Trigger: A new blog post is created in Blogs API (POST /blogs/posts).
Actions: create/update an email in emails/builder and schedule the post handling in Dubb.
POST /blogs/posts
title, slug, content, authorId, status
Trigger: Blog post is updated (PUT /blogs/posts/:postId).
Actions: refresh email templates via emails/builder and push a follow-up schedule.
PUT /blogs/posts/:postId
postId, title, slug, content, status
Trigger: New blog draft is created (POST /blogs/posts).
Actions: publish to blog and send kickoff email via emails/builder.
POST /blogs/posts
title, slug, scheduleDate, authorId, status
Zero-code automation to align blog content with emails and campaigns.
Fast time-to-value with visual builders and triggers.
Unified content workflow in a single workspace.
Key elements include endpoints, triggers, actions, and fields; core processes cover authentication, data mapping, error handling, and retries.
API stands for Application Programming Interface; a structured set of endpoints that lets apps talk to each other.
A URL-friendly identifier used to reference a blog post within the system.
A real-time notification sent from one app to another when a specified event occurs.
A specific URL you call to perform an action or retrieve data from an API.
When a new blog post is published, generate a summarized email and send it to subscribers via the Email Builder.
Set up a weekly digest email that aggregates recent posts and highlights from your Dubb workspace.
Embed slug-based previews and shareable snippets to boost click-through rates.
Obtain the client ID, client secret, and set the scope to emails/builder.readonly.
Map Blogs API endpoints to Dubb actions and configure webhooks where needed.
Run end-to-end tests to verify data flows, mapping, and error handling before going live.
Yes—initial setup can be done in a sandbox or with test data to validate triggers and actions. You’ll configure OAuth 2.0 or API key-based authentication and verify token scopes before touching production data. Once confirmed, you can enable live flows.
For basic syncing, you’ll typically use endpoints to create and update blog posts (POST /blogs/posts, PUT /blogs/posts/:postId) and to manage email templates (GET/POST emails/builder) plus schedule interactions. This covers core data transfer and notification flows.
Yes. Use a dedicated test workspace, post drafts, and simulated events. Validate triggers, data mappings, and error handling without impacting your customers. Run end-to-end tests before going live.
The required scope is emails/builder.readonly for most read operations. Depending on actions, you may need write permissions such as emails/builder or boards endpoints for posts. Always scope minimally and adjust as needed.
Map common fields like title, slug, content, authorId, and status between Blogs API and the Email Builder templates. Use consistent data types and validate required fields before triggering actions.
If an endpoint returns an error, review the HTTP status, error body, and authentication. Implement retries with exponential backoff and log failures for debugging. Contact support if errors persist.
A sandbox or test environment is often available. Use it to simulate live flows, test tokens, and verify mappings. When ready, migrate configurations to production with careful change control.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
