How to Connect LazyRelay to Make

Schedule and publish social posts from a Make scenario, and start a scenario when a post is confirmed live or fails.

Plain status: LazyRelay does not have its own app in Make's directory yet. Everything below uses Make's built-in HTTP and Webhooks modules against LazyRelay's public API, which works today and needs no approval from anyone.

What you can build

1. A new row in a Google Sheet or Airtable content calendar schedules a post to the right platform.
2. A new blog post or product schedules a promotion, with the image uploaded for you.
3. A post confirmed live (or one that fails) starts a scenario that logs it, alerts a channel, or emails a client.

Set up

1. In your LazyRelay dashboard, open the API Keys tab and create a key. Copy it: it is shown once.
2. In Make, add the module HTTP, then Make a request. Everything below uses this module.
3. Set the header Authorization to Bearer lzr_live_your_key_here on each request. In Make you can store the key once in a scenario variable or a Data store so it is not pasted into every module.

Step 1: find your account ids

Add an HTTP request with Method GET and URL https://lazyrelaylazyrelay-backend.onrender.com/api/social-accounts. Set Parse response to Yes. Each item has an id and a platform. You only need to do this once, or you can map it into a lookup.

Step 2: schedule a post

Add an HTTP request: Method POST, URL https://lazyrelaylazyrelay-backend.onrender.com/api/scheduled-posts, Body type Raw, Content type JSON (application/json), and a request body like this:

{
  "socialAccountId": "the account id from step 1",
  "content": "Your post text",
  "scheduledFor": "2026-10-01T09:00:00Z",
  "mediaUrl": "https://example.com/image.jpg",
  "tags": ["launch"]
}

Turn on Parse response. If LazyRelay refuses the post, the response says exactly why (a missing TikTok privacy level, a Pinterest board, a plan limit) in an error field, and Make shows it as a failed run. To ask what a platform needs before you build the scenario, call GET /api/platforms/rules?platform=tiktok.

Post to several platforms by adding one request per account, or by using Make's Iterator over a list of account ids.

Step 3: upload an image or video

To attach a file that is not already at a public web address, add an HTTP request with Method POST, URL https://lazyrelaylazyrelay-backend.onrender.com/api/media/upload, Body type Multipart/form-data, and one field named file of type File. The answer contains a url. Use that as mediaUrl in step 2.

Step 4: start a scenario when a post goes live or fails

1. In Make, start a scenario with Webhooks, then Custom webhook and copy its address.
2. In LazyRelay, open Settings, then Webhooks, add an endpoint with that address, and pick the events: post.verified (confirmed live), post.failed, post.unconfirmed or channel.needs_reconnect. Press Send test so Make learns the data shape.
3. Build the rest of the scenario. The data includes the post text, the platform, and the reason when something failed.

Webhooks are set up by a person in the dashboard, not through an API key. That is deliberate: a leaked key can never be used to point your webhooks somewhere else. Each delivery is signed with your endpoint's secret so a receiver can check it came from LazyRelay; the details are in the API docs.

Everything else the API can do

The full API is described as OpenAPI at /api/openapi.json. Anything that reads OpenAPI (Postman, code generators, and tools that build Make or n8n requests from a spec) can use it. It covers scheduling, drafts, approvals, client review links, analytics, comments, saved posting times, RSS feeds and more.