Use your Blogs API credentials to authorize DonorDock. The connection uses the provided scope (emails/builder.readonly) to securely access blog data and email-related resources.
Approve the connection in your Blogs API dashboard to allow DonorDock to read and manage blog content and related emails. This completes the OAuth or API key setup and enables automated workflows.
– GET emails/builder – WRITE emails/builder – POST emails/builder – POST /emails/builder/data – DELETE /emails/builder/:locationId/:templateId – READONLY emails/schedule – 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 or updated in Blogs API to automatically queue a corresponding update in DonorDock for donor communications.
Actions include: create or update posts (POST /blogs/posts, PUT /blogs/posts/:postId), check slug availability (GET /blogs/posts/url-slug-exists), fetch categories (GET /blogs/categories), and fetch authors (GET /blogs/authors).
Endpoints used: POST /blogs/posts, PUT /blogs/posts/:postId, GET /blogs/posts/url-slug-exists, GET /blogs/categories, GET /blogs/authors
Key fields: postId, slug, title, content, authorId, categoryId
Trigger when an email template is created or scheduled in Blogs API to align with DonorDock email campaigns.
Actions include: manage email templates (GET/POST/DELETE on emails/builder), schedule emails (GET /emails/schedule, READONLY endpoint), and trigger sends from DonorDock.
Endpoints used: GET emails/builder, POST emails/builder, GET emails/schedule
Key fields: templateId, locationId, subject, body
Trigger when slug status or post readiness needs verification before publishing to ensure clean URLs and taxonomy alignment.
Actions include: check slug availability (GET /blogs/posts/url-slug-exists), validate and create/update posts (POST /blogs/posts, PUT /blogs/posts/:postId), and perform slug checks before publish.
Endpoints used: GET /blogs/posts/url-slug-exists, POST /blogs/posts, PUT /blogs/posts/:postId
Key fields: slug, postId, title
No-code setup lets you connect via OAuth or API keys without writing code, accelerating the time-to-value.
Automate blog-to-donor workflows, such as posting new blogs and triggering targeted donor emails, all from a single dashboard.
Centralized data and real-time syncing reduce manual work and improve audience engagement.
Key terms and processes you’ll encounter when integrating Blogs API with DonorDock are defined below to help you navigate setup and ongoing maintenance.
API stands for Application Programming Interface. It provides a set of endpoints that DonorDock can call to read and manage blog data within Blogs API.
A URL-friendly string that uniquely identifies a blog post and appears in the post URL.
A blog entry created, updated, or published via the Blogs API.
The process of granting DonorDock access to the Blogs API, typically via OAuth or API keys, to securely interact with data.
When a new blog post is published in Blogs API, automatically trigger a DonorDock email to inform donors and invite engagement.
Pull blog categories and author data to tailor newsletters, increasing relevance and open rates.
Send donor-facing digests highlighting recent posts by authors they follow or related topics.
Collect your Blogs API credentials or set up OAuth, then authorize DonorDock to access the required scopes.
Choose the endpoints you’ll use (blogs/posts, blogs/categories, blogs/authors, etc.) and map fields like postId, slug, authorId, and categoryId to DonorDock fields.
Test in a sandbox, verify data sync and trigger flows, then deploy to production with monitoring.
The Blogs API integration with DonorDock enables you to connect blog data and email workflows without custom code. It lets you automate blog-driven donor communications by pulling posts, authors, and categories into DonorDock and triggering emails or newsletters when new content is published. This keeps donors informed and engaged using the same platform you manage campaigns in. With secure authentication and well-defined endpoints, you can set up reliable data flows that scale with your content strategy.
Basic setup is designed to be no-code. You can connect via OAuth or API keys, map fields, and configure triggers and actions inside DonorDock’s UI. Advanced customization is possible but not required for common use cases. If you need more complex logic, you can extend workflows with conditional steps and parallel actions.
For basic syncing, essential endpoints include: POST /blogs/posts to create posts, PUT /blogs/posts/:postId to update posts, GET /blogs/posts/url-slug-exists to check slug availability, GET /blogs/categories for categories, and GET /blogs/authors for author data. You can expand later to include blog checks and slug validation as needed.
Authentication typically uses OAuth with the Blogs API or API keys. DonorDock will guide you through granting access and selecting the necessary scopes. Once approved, DonorDock can read blog data and manage related email workflows securely.
Slug conflicts are avoided by checking slug availability before publish (GET /blogs/posts/url-slug-exists). If a slug already exists, you’ll be prompted to adjust the slug or post title. Consistent slug rules help maintain clean URLs and avoid duplicate content.
Yes. You can fetch authors and categories using GET /blogs/authors and GET /blogs/categories. This data allows you to segment content, personalize communications, and route posts to the right audience within DonorDock.
Best practices include validating data mappings, testing triggers in a sandbox, logging successful and failed syncs, and setting up alert notifications for failures. Start with a small subset of posts and gradually scale to full content syncing.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
