Access is secured with OAuth tokens and an API key. Use the scope specified for reading builder data (emails/builder.readonly) to retrieve blog information as needed by the connector.
Authenticate BigMarker with an OAuth app and store client credentials in the connector. This enables secure access to webinars, notifications, and attendee data.
Key endpoints used across the integration include: GET emails/builder; POST /emails/builder/data; GET emails/schedule; POST /blogs/posts; PUT /blogs/posts/:postId; GET /blogs/categories; GET /blogs/authors; GET /blogs/posts/url-slug-exists; GET /blogs/categories; GET /blogs/authors.
Trigger: when a new post is published in Blogs API, automatically push it to BigMarker as a post or announcement.
Actions: create a BigMarker update or event, fetch post data, and attach the post slug.
POST /blogs/posts
title, slug, excerpt, content, authorId
Trigger: BigMarker event (like attendee status change) updates a blog post in Blogs API.
Actions: PUT /blogs/posts/:postId to update content and status; optionally POST /blogs/posts to create edits.
PUT /blogs/posts/:postId
postId, title, content, status
Trigger: new or updated categories/authors in Blogs API refresh related BigMarker displays.
Actions: GET /blogs/categories and GET /blogs/authors to pull fresh data; POST /blogs/categories to add new categories.
GET /blogs/categories; GET /blogs/authors
categoryId, authorId
Build complex workflows visually—no custom code required.
Automate content publishing and attendee communications in one flow.
Scale easily as you add more blogs, categories, and events.
This section defines key elements like endpoints, triggers, actions, data mappings, authentication methods, and error handling used in the integration.
A specific URL path and HTTP method used to perform an action against an API.
A URL-friendly string derived from the post title used in the blog URL.
The process of proving identity to access APIs, typically with tokens or keys.
A callback URL that receives real-time notifications when an event occurs.
Automatically publish a recap post after each webinar in BigMarker and attach it to your Blogs API library.
Pull author bios from Blogs API and display on BigMarker event pages and show notes.
Queue topics from Blogs API to suggested BigMarker webinar topics and reminders.
Create and configure API credentials in both platforms; securely store tokens.
Link events like new posts or attendees to the corresponding API calls.
Run end-to-end tests and monitor the data flows before going live.
No-code workflows are available through our visual builder, so you can set up triggers, actions, and mappings without writing code. You’ll configure the integration with a few clicks and test data flows in a safe sandbox.
For a basic sync you’ll typically use endpoints like GET /blogs/posts, POST /blogs/posts, GET /blogs/categories and GET /blogs/authors. This gives you publishing, editing, and taxonomy alignment between platforms.
Security is maintained with OAuth tokens, scoped permissions, and encrypted storage. If a token revokes or expires, you can refresh it and retry the operation.
Yes. The mapping schema lets you tailor fields such as title, slug, content, status, category, and author to meet your content workflows.
If a call fails, the system retries automatically and logs the error details. You can review retries and adjust retry rules in the dashboard.
Compatibility depends on your BigMarker plan and API access. In most cases, features work across standard plans with proper credentials.
Logs are accessible in the integration dashboard, with per-call details, timestamps, and outcome status, plus export options.
Due to high volume, we will be upgrading our server soon!
Complete Operations Catalog - 126 Actions & Triggers
