Relay · Social publishing API and dashboard

Post once. Land everywhere. Know exactly what happened.

Connect your accounts once. Send one post to all of them. Get a straight answer from every network in one place, the moment it lands.

This one is being built now. Join the early access list and we will email you once, when it opens.

Every destination on one screen.

Send a post and watch it go out. Each account reports back on its own line, with the reason when a network says no and the time when it is waiting for later.

New postThu 4 Sep

Scheduling is live. Pick a time, pick your accounts, and we hold the post until then. Full notes in the changelog.

  • Northwind@northwind
  • Northwind Careers@northwind-jobs
  • Pine & Board@pineboard
Send nowor schedule for later
What happenedone post, three answers
  • Northwind@northwinddelivered

    Sent at 09:00. Open the post on the network.

  • Northwind Careers@northwind-jobsscheduled

    Waiting for 14:00 today. Cancel or move it any time before then.

  • Pine & Board@pineboardneeds a fix

    This network trims captions at a shorter limit. Shorten the last line, or write a version just for this account, and send again.

  1. 09:00:02Post checked against all three accounts
  2. 09:00:02Two accounts accepted, one sent back a reason
  3. 09:00:03Northwind delivered
  4. 09:00:03Careers queued for 14:00

Sample view with example accounts.

01

Connect once, publish for months

Add each account through its own sign-in, group them the way you think about them, and publish to a whole group in one go. Relay watches the connections and tells you when one needs renewing, before a post fails because of it.

  • Sign in through each network, no passwords held here
  • Group accounts by brand or team and post to the group
  • A heads-up when a connection needs attention
Connected accounts
  • Northwind@northwindBrandConnected
  • Northwind Careers@northwind-jobsCareersConnected
  • Pine & Board@pineboardBrandRenew soon

Publish to a group and every account in it goes out together.

02

Caught before it goes out

Every network has its own rules about length, images, links and formatting. Relay checks your post against each destination first, so you fix a caption in the composer instead of hearing from a customer that half the launch never posted.

  • Checked per destination before anything is queued
  • Plain reasons you can act on, not error codes
  • Per-network tweaks when one needs different wording
Before you send

The new scheduling view is live. Pick a time, pick your accounts, and Relay holds the post until then.northwind.example/changelog

  • Northwind, ready to send
  • Northwind Careers, ready to send
  • Pine & Board, this network trims the caption. Shorten it by a line or write a version just for this account.
03

One timeline, every outcome

Delivered, scheduled, needs attention. Each destination gets its own line with the time, the link when there is one, and a retry when it makes sense. Send the same events into your own tools with webhooks.

  • A result per destination, never one vague summary
  • Retry or cancel from the same screen
  • Webhooks and logs for your own dashboards
This post
  • NorthwindDelivered 09:00, view post
  • Northwind CareersScheduled for 14:00 today
  • Pine & BoardNot sent, caption too long. Retry after editing.

The same three events reach your webhook, in the same order.

04

Schedule it and stop worrying

Pick a time and Relay holds the post until then. Send the same request twice by accident and it hands back the original instead of posting again, which is the failure everybody remembers and nobody enjoys explaining.

  • Queue posts for a date and time
  • A repeated request never becomes a second post
  • Cancel anything that has not gone out yet
Queue
Thu 4 Sep09:003 accounts
  • Launch noteQueued, cancel any time before it sends
  • Hiring postQueued for Friday

Send the same request twice and you get this post back, not a second one.

Who it is for

Built for the people who do this every week.

  • Product teams

    Release notes, status updates and launches that have to reach the company accounts at the same time, without three people copying the same paragraph.

  • Agencies and studios

    Many brands, many accounts, one place to see what went out today and what needs a second look.

  • Builders

    One API and a TypeScript SDK, so publishing becomes a few lines in your own product instead of an integration project per network.

Questions

Good things to ask.

When can I use it?

Relay is being built now. Join the early access list and we will email you once, when the first version opens. The people on that list get the first invitations.

Which networks will it publish to?

The first ones are the networks with a proper public API and a sandbox to test against, and each is named here once it works end to end. We would rather list two that work than ten that might.

Will it post without me?

It posts what you wrote, when you said. Scheduling is yours to set. Anything an automation or an assistant drafts is shown to you in full, with its destinations, before it goes anywhere.

What happens to my account logins?

You connect through each network's own sign-in. Tokens are encrypted, never shown back to you or written to a log, and you can disconnect an account whenever you want.

Can I try it without touching a real account?

Yes. Sandbox mode talks to test destinations that cannot reach anyone, so you can build the whole flow before you connect anything real.

Early access

Be first in line for Relay.

Leave your email and tell us which networks matter to you. We read every reply, and the first invitations go to this list.

One email when there is something to send. Nothing else, no newsletter.

This one is being built now. Join the early access list and we will email you once, when it opens. In the meantime, Drift is ready today.