Make

Make reaches Pozy with its built-in HTTP app for actions and Webhooks app for triggers. Everything below uses those two apps, so it works on every Make plan.

You need a Pozy API key (Developers → API keys in the dashboard) and at least one connected account.

#Make your first request

To avoid pasting the key into every module, store it once in a data store or a scenario variable and map it into the header.

#Create a post

Add another HTTP → Make a request module:

Request content, with values mapped from earlier modules:

{
  "content": "{{1.text}}",
  "platforms": [
    { "platform": "linkedin", "accountId": "6650f1c2a8b4e3d2c1b0a333" }
  ],
  "mediaItems": [
    { "type": "image", "url": "{{1.imageUrl}}" }
  ],
  "publishNow": true
}

Remove mediaItems for a text-only post.

#Schedule for later

Send a local time plus a timezone instead of publishNow:

{
  "content": "{{1.text}}",
  "platforms": [{ "platform": "linkedin", "accountId": "6650f1c2a8b4e3d2c1b0a333" }],
  "scheduledFor": "{{formatDate(addDays(now; 1); "YYYY-MM-DD")}}T09:00:00",
  "timezone": "Europe/Madrid"
}

This posts at 9:00 in Madrid tomorrow. Other useful expressions:

#Different text per platform

Use one request with customContent per platform rather than a Router with several modules. It keeps the post as one item in Pozy, with one status to watch:

{
  "content": "{{1.title}}",
  "platforms": [
    { "platform": "linkedin", "accountId": "6650f1c2a8b4e3d2c1b0a333", "customContent": "{{1.longSummary}}" },
    { "platform": "twitter", "accountId": "6650f1c2a8b4e3d2c1b0a444", "customContent": "{{1.shortSummary}} {{1.url}}" }
  ],
  "publishNow": true
}

#Trigger a scenario from Pozy

{
  "name": "Make: published posts",
  "url": "https://hook.eu1.make.com/abc123",
  "events": ["post.published"],
  "customHeaders": { "X-Hook-Token": "a-long-random-string" }
}

#Make sure the call came from Pozy

In the webhook's advanced settings, turn on Get request headers. Add a filter right after the webhook that only lets bundles through when the X-Hook-Token header equals the value you set in customHeaders.

For full signature checks, turn on JSON pass-through too, so the webhook outputs the body exactly as sent, and compare X-Pozy-Signature with sha256(<raw body>; "hex"; "<endpoint secret>") in the filter. Make's sha256 function returns an HMAC when you give it a key.

Respond within 5 seconds. A custom webhook answers immediately by default, which is what you want. Pozy retries a delivery that fails, so the same event can arrive twice; if that matters, keep processed X-Pozy-Event-Id values in a data store and skip repeats.

#Scenario ideas

• Content calendar. Google Sheets → Watch Rows, then HTTP creates the post from the row, with Idempotency-Key set to the row number.
• Posting from your app. Your app sends JSON to a Make custom webhook; an HTTP module turns it into a Pozy post.
• Retry failed posts every hour. Schedule every hour, GET /v1/posts?status=failed, an Iterator over posts, then POST /v1/posts/{postId}/retry for each.
• Review alerts. Custom webhook on review.new, a filter on low ratings, then Slack or email.

#When a module fails