Create an API key in your GHL developer console and grant TinyEmail the required scope: emails/builder.readonly. This enables TinyEmail to read email templates and builder data for seamless automation.
Connect TinyEmail to your GHL account using OAuth, authorizing access to endpoints such as blogs/posts, emails/builder, and blogs/categories so you can automate content workflows without code.
Core endpoints used in typical workflows include: GET emails/builder; POST emails/builder; POST /emails/builder/data; GET emails/schedule; POST /blogs/posts; PUT /blogs/posts/:postId; GET /blogs/posts/url-slug-exists; GET /blogs/categories; GET /blogs/authors.
Trigger: When a new email draft is saved in TinyEmail, automatically create a corresponding blog post draft in Blogs API.
Actions: Use POST /blogs/posts to create the post; update with PUT /blogs/posts/:postId; validate slug with GET /blogs/posts/url-slug-exists.
POST /blogs/posts
title, slug, content, author, categories
Trigger: Edit an email template to update the corresponding blog post.
Actions: Update content with PUT /blogs/posts/:postId; optionally create variants with POST /blogs/posts.
PUT /blogs/posts/:postId
postId, title, content, slug
Trigger: Schedule a blog post to publish at a future date when a TinyEmail campaign is scheduled.
Actions: Use POST /blogs/posts with publishDate; verify slug with GET /blogs/posts/url-slug-exists.
POST /blogs/posts
title, slug, content, publishDate
Fast, code-free setup: connect APIs and start automating in minutes using built-in builders.
Seamless content workflows: auto-create, update, and schedule blog posts from email templates.
Publish on schedule with confidence: coordinate posts with campaigns without writing code.
This glossary explains common terms used in the guide to help you navigate GHL, Blogs API, and TinyEmail integrations.
A specific URL that performs a function in a web service.
A URL-friendly string used to identify a blog post in a readable, SEO-friendly way.
A callback URL that triggers an action when a defined event occurs in a service.
The date and time a blog post goes live on your site.
Turn high-performing email templates into blog drafts with automatic title and slug generation, ready for review.
Link email send triggers to blog post publishing, ensuring fresh content aligns with campaigns.
Automatically assign posts to multiple categories using the blogs endpoints for broader reach.
Create an API key in GHL and grant the necessary scopes (emails/builder.readonly, blogs/*) for TinyEmail.
Choose the endpoints you will use (emails/builder, blogs/posts, blogs/categories) and align fields like title, slug, and content.
Run tests to verify slug existence, content sync, and scheduled publish flows before launching.
No heavy coding required. TinyEmail provides built-in builders and triggers to automate workflows between emails and blogs. You’ll configure connections and map fields using a visual interface, then test the flow before going live. If you know basic API concepts, you’ll find the setup straightforward, but even beginners can succeed with the step-by-step prompts.
For basic blog publishing, you’ll typically need: POST /blogs/posts to create posts, PUT /blogs/posts/:postId to update, and GET /blogs/posts/url-slug-exists to ensure unique slugs. You may also use GET /blogs/categories and GET /blogs/authors to enrich posts with metadata. Optional endpoints like GET emails/builder help pull in templates for content ideas.
Use GET /blogs/posts/url-slug-exists before publishing to verify slug uniqueness. If a slug exists, generate a new one automatically or prompt for a user-friendly variation. Keeping slug checks in the workflow prevents collisions and improves SEO.
Yes. You can schedule posts by providing a publishDate when creating a post with POST /blogs/posts or by updating an existing post with PUT /blogs/posts/:postId. This lets you align publishing with campaigns and promotions without manual steps.
API keys are created in the GHL developer console. Save the key and assign TinyEmail the required scopes (for example, emails/builder.readonly and relevant blogs scopes). Then configure the app in TinyEmail to use that key for authenticated requests.
Required scopes vary by workflow but typically include emails/builder.readonly and blogs/* (to read templates and manage posts). If you plan to read authors, categories, or update posts, include blogs/authors, blogs/categories, and blogs/posts scopes as needed.
API documentation is available in your GHL developer portal and the TinyEmail integration guide. Both resources provide endpoint details, example requests, and best practices for authentication, field mapping, and error handling.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
