To start, obtain your API key or OAuth token from the Blogs API dashboard and grant access to TidyCal. Use the provided scope to limit permissions and protect credentials.
Authorize TidyCal to read and write to your Blogs data. This ensures seamless creation and updates of posts from bookings.
Endpoints covered in this guide include: GET /blogs/posts; POST /blogs/posts; PUT /blogs/posts/:postId; GET /blogs/posts/url-slug-exists; GET /blogs/categories; GET /blogs/authors; POST /blogs/post-update.write; GET /blogs/posts
Trigger: when a new booking is created in TidyCal, create a draft blog post in Blogs API.
Actions: POST /blogs/posts to create the post; PUT /blogs/posts/:postId to update after edits; GET /blogs/posts/url-slug-exists to ensure a unique slug.
POST /blogs/posts
title, content, slug, author, categories
Trigger: when a TidyCal booking is updated, update the linked blog post.
Actions: PUT /blogs/posts/:postId to update; optionally POST /blogs/post-update.write to log changes; refresh content fields.
PUT /blogs/posts/:postId
postId, title, content, slug
Trigger: before publish, verify the slug is not already in use.
Actions: GET /blogs/posts/url-slug-exists to check; if available, proceed with POST /blogs/posts; otherwise, prompt for an alternative slug.
GET /blogs/posts/url-slug-exists
slug
Automate content creation without writing a line of code by mapping bookings to post fields.
Keep your blog in sync with events, launches, and promotions automatically.
Save time and reduce manual errors through repeatable workflows.
Key elements include endpoints (URLs and HTTP methods), triggers (events in TidyCal), actions (API calls), data fields, and slug checks used to prevent duplicates.
An application programming interface that lets apps talk to each other through defined endpoints.
A URL-friendly, unique identifier used in blog post URLs.
A specific URL combined with an HTTP method that performs an action, such as GET or POST.
A lightweight callback that sends data in real time when an event occurs.
Automatically generate weekly roundups from booked events and publish them to your blog via the Blogs API.
Archive high-demand events into timeless posts to boost SEO.
Pre-build templates for recurring event types to speed publishing.
Obtain API credentials and grant TidyCal access to Blogs data.
Choose endpoints and align data fields between TidyCal bookings and blog posts.
Run tests, verify slug uniqueness, and push to production.
No coding is required. This guide walks you through a no-code setup using the UI to connect endpoints and map fields. You can trigger blog creation from TidyCal events without writing code. The UI guides you through authentication, endpoint selection, and field mapping so you can start automating quickly.
Start with essential endpoints: GET /blogs/posts to fetch posts, POST /blogs/posts to create, and PUT /blogs/posts/:postId to update. Then add slug checks with GET /blogs/posts/url-slug-exists to prevent duplicates. As you gain control, you can layer more endpoints for categories and authors.
Yes. You can automate from a booking to a draft or published post. Set up a trigger on a new booking to create a post draft, then publish after review. Use the slug check to ensure clean URLs before going live.
Slug conflicts happen when two posts share the same slug. Use the existing slug existence endpoint to validate and generate a unique slug before posting. If a conflict arises, modify the slug with a suffix and retry the publish.
Security is as strong as your credentials. Use OAuth or API keys, restrict scopes, rotate keys, and store tokens securely. The app connector uses HTTPS and follows standard security best practices.
Yes. You can customize fields in the mapping layer. Map booking fields like summary, notes, or location to title, content, and tags in your blog posts, then save presets for reuse.
API credentials are found in the Blogs API dashboard under your account settings. Rotate keys regularly, use separate keys for test and production, and revoke access when needed.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
