Skip to main content

Overview

Connect Marky to your automation stack. Common workflows:
  • Blog published → social posts — RSS trigger → create post in Marky → schedule
  • New lead in CRM → welcome posts — CRM trigger → create branded content
  • Weekly content batch — Schedule trigger → create a week of posts from your templates or sheet data

Zapier setup

1. Create a Zap with a Webhooks action

Zapier doesn’t have a native Marky integration (yet), so use the Webhooks by Zapier action. Trigger: Choose your trigger (RSS, Google Sheets, CRM, Schedule, etc.) Action: Webhooks by Zapier > Custom Request
Method: POST
URL: https://api.mymarky.ai/api/businesses/your-workspace-id/posts
Headers:
  Authorization: Bearer mk_live_your_key_here
  Content-Type: application/json
Data:
{
  "caption": "{{trigger_content}}",
  "restrict_publish_to": ["instagram", "linkedin"]
}

2. Schedule the post (optional)

Add another Webhooks > Custom Request step:
Method: POST
URL: https://api.mymarky.ai/api/businesses/your-workspace-id/posts/{{post_id_from_step_1}}/schedule
Headers:
  Authorization: Bearer mk_live_your_key_here
  Content-Type: application/json
Data:
{
  "scheduled_publish_time": "2026-12-01T14:00:00Z"
}

Make (Integromat) setup

1. Create a scenario with an HTTP module

Trigger: Your choice (RSS, Webhook, Schedule, etc.) Action: HTTP > Make a request
FieldValue
URLhttps://api.mymarky.ai/api/businesses/your-workspace-id/posts
MethodPOST
HeadersAuthorization: Bearer mk_live_your_key_here
Body typeRaw > JSON
Body{"caption":"{{content}}","restrict_publish_to":["instagram"]}

2. Schedule (optional)

Add another HTTP module to schedule the post using the ID from step 1.

Rate limits

Each API key can make:
  • 100 requests per minute
  • 2,000 requests per day
  • 10,000 requests per week
A weekly batch of 10 posts uses ~20 requests, well within limits. If you hit a cap, you get a 429 response with a Retry-After header telling you how many seconds to wait.

Tips

  • Schedule in Marky, not your automation tool: Use the /businesses/{business_id}/posts/{id}/schedule endpoint to let Marky handle publishing at the right time for each platform.
  • Use the library: Push content into Marky’s library via /api/businesses/{business_id}/library/files for reuse across multiple posts.