Authenticate requests from Runrun-it to the Blogs API using secure keys or OAuth credentials, and rotate tokens regularly to maintain security.
Runrun-it connects to Blogs API via a dedicated API key or OAuth client, following standard security practices.
Essential endpoints include: GET emails/builder, POST emails/builder, POST /emails/builder/data, PUT /blogs/posts/:postId, POST /blogs/posts, GET /blogs/posts/url-slug-exists, GET /blogs/categories, GET /blogs/authors, and GET /blogs/categories.
Trigger when a new blog post is created or updated in Runrun-it, then assemble and send an email using the Emails Builder endpoints.
Actions: create email templates, populate with post data, schedule or send via emails/builder endpoints.
Methods/Paths: GET emails/builder, POST emails/builder, POST /emails/builder/data
Required fields: locationId, templateId, subject, body, postId, postTitle
Trigger when a blog post is created or updated in Runrun-it, then push changes to Blogs API to reflect the post.
Actions: POST /blogs/posts to create, PUT /blogs/posts/:postId to update, and check slug with GET /blogs/posts/url-slug-exists.
Methods/Paths: POST /blogs/posts, PUT /blogs/posts/:postId, GET /blogs/posts/url-slug-exists
Required fields: postId, title, content, categoryId, authorId, slug
Trigger: validate slug and taxonomy prior to publishing to ensure consistency and discoverability.
Actions: call GET /blogs/posts/url-slug-exists, GET /blogs/categories, and GET /blogs/authors to verify metadata.
Methods/Paths: GET /blogs/posts/url-slug-exists, GET /blogs/categories, GET /blogs/authors
Required fields: slug, categoryId, authorId
Automate routine content workflows without writing code, using visual triggers and actions.
Centralize data flow between your CMS and marketing tools for faster publishing.
Accelerate time-to-publish with templated emails and blog posts driven by triggers.
This section explains the main elements: endpoints, triggers, actions, and fields used in the integration.
An application programming interface that allows software to communicate and exchange data securely.
A specific URL in an API that performs a defined action when called.
The process of verifying identity to access protected resources, typically via keys or OAuth tokens.
A URL-friendly identifier used in blog post URLs to improve readability and SEO.
Automatically pull the latest posts and assemble a digest email using the Emails Builder to send to subscribers.
Check slug existence and publish posts with SEO metadata via Runrun-it triggers.
Create blog posts in Runrun-it and push summaries to social platforms through the Blogs API.
Obtain API keys or OAuth credentials and grant Runrun-it access to the Blogs API.
Set up triggers for new posts, and map fields to Runrun-it templates.
Run test posts, verify slug checks, and monitor logs for any issues.
Essential endpoints include GET emails/builder, POST emails/builder, POST /emails/builder/data, and GET /blogs/posts/url-slug-exists for slug checks. You’ll also use POST /blogs/posts to create posts. These endpoints enable content-driven automation between Blogs API and Runrun-it. Additionally, GET /blogs/categories and GET /blogs/authors help populate taxonomy and author fields during content creation.
Authentication is typically accomplished via API keys or OAuth credentials. Securely store tokens, rotate them regularly, and associate them with your Runrun-it instance. Use scoped access (emails/builder.readonly, blogs/post.write, etc.) to follow the principle of least privilege. If you’re using OAuth, ensure redirect URIs are whitelisted and refresh tokens are managed properly.
Yes. Use the slug existence endpoint GET /blogs/posts/url-slug-exists before publishing to ensure uniqueness. This helps prevent duplicate content and preserves SEO. You can programmatically adjust the slug or title if a conflict is detected.
Map Runrun-it blog fields (title, content, categoryId, authorId, slug) to the corresponding templates in the Emails Builder. Use POST /emails/builder/data to populate email templates with blog data, and then send or schedule emails via GET emails/builder or POST emails/builder endpoints.
GET /blogs/categories and GET /blogs/authors provide taxonomy and author data. You can pull this information into Runrun-it to ensure posts are categorized and credited correctly. This helps maintain consistency across platforms.
Yes. The integration is designed for no-code setups using triggers, actions, and templates. Start with a basic trigger for new posts, then add templates and schedules without writing code. You can extend functionality gradually as you validate the workflow.
Logs and errors are visible in Runrun-it’s task history and in the Blogs API request logs. Monitor for failed authentications, 4xx/5xx responses, and data mismatches. Set up alerting where possible to catch issues quickly.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
