To authenticate, authorize the Blogs API connection with the scope emails/builder.readonly. This ensures read access to email builder and blog related endpoints while keeping your data secure. Use your GHL API credentials to authorize the connection from Scoop-it.
Scoop-it uses OAuth tokens tied to your app user to securely access the connected GHL account. After initial consent, token refresh happens automatically so your automation stays online.
GET emails/builder; 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
Trigger: when a new blog post is created in Scoop-it to publish via the Blogs API, or when a draft is ready to publish.
Actions: publish a new post with POST /blogs/posts, update posts with PUT /blogs/posts/:postId, and verify slug availability with GET /blogs/posts/url-slug-exists.
Method paths example: POST /blogs/posts for create, PUT /blogs/posts/:postId for update, GET /blogs/posts/url-slug-exists to check slug existence.
Required fields: title, content, slug, status, authorId, categories.
Trigger: a new category is added in Blogs API or mapping changes are needed in Scoop-it.
Actions: fetch and map categories via GET /blogs/categories; align with Scoop-it’s category fields.
Method paths example: GET /blogs/categories to retrieve categories; map to Scoop-it fields.
Fields: name, slug, description.
Trigger: new or updated author in Blogs API.
Actions: fetch authors via GET /blogs/authors; create/update as needed; map to Scoop-it author fields.
Method path example: GET /blogs/authors to retrieve authors; update as supported.
Fields: name, bio, slug, avatar_url.
Automate blog publishing to multiple channels without writing code.
Maintain SEO-friendly slugs and consistent author/category metadata across systems.
Centralized workflow: schedule, publish, and monitor from one dashboard.
Key elements include API endpoints, authentication, triggers, actions, and data fields. The processes describe how data flows from Scoop-it to GHL and back.
An API is a set of rules and tools for building software and applications. It defines how components interact.
A blog entry consisting of a title, content, and metadata such as author, category, and slug.
A specific URL in an API that performs a defined action, like creating or fetching a post.
A check to determine if a URL-friendly slug already exists for a blog post before publishing.
Capture notes in Scoop-it and auto-create drafts in Blogs API, then publish on schedule.
Generate SEO-friendly slugs and schedule posts automatically.
Sync author bios from Blogs API into Scoop-it for richer previews and attribution.
In your GHL account, grant the Blogs API scope and authorize Scoop-it to access the required endpoints.
Choose the endpoints you’ll use (blogs/posts, blogs/categories, blogs/authors, etc.) and map to Scoop-it fields.
Test the integration with a sample post, verify slug exists, publish, and monitor results.
No coding is required; the visual setup lets you map fields between Scoop-it and the Blogs API with a few clicks. You can customize triggers and actions without touching code. If you need advanced control, you can adjust settings for edge cases in the connector. The goal is to get you running quickly with a reliable workflow.
The integration leverages endpoints such as blogs/posts, blogs/categories, and blogs/authors to create, update, fetch, and map data. You’ll see common actions like creating posts, updating posts, and checking slug availability, ensuring alignment across Scoop-it and the Blogs API.
There are no hard-coded daily post limits in the connector itself; limits depend on your GHL plan and API quotas. For large campaigns, batch your publishes and monitor usage to stay within rate limits.
Yes. Category and author syncing is supported. You can map categories via GET /blogs/categories and authors via GET /blogs/authors to keep metadata consistent across systems.
OAuth tokens are refreshed automatically in standard configurations. If a token expires, re-authentication prompts appear and the connection can be re-established without losing prior mappings or workflow setups.
Slug existence checks use GET /blogs/posts/url-slug-exists. If a slug already exists, you can modify it or generate a unique variant before publishing to avoid conflicts.
Error logs and run histories are accessible within the Scoop-it app. You can view endpoint responses, retry failed actions, and drill into issues to resolve problems quickly.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
