Skip to content

Find your workflow

For growth and marketing ops

Campaigns that publish themselves, on schedule.

You are the person who owns the handoff between a campaign plan and the networks. When that handoff fails, nobody notices until the launch window has passed, so the pipeline needs to be observable.

  • Team 2 to 15 people
  • Scope campaigns, not product code
  • Signals webhooks in and out

The problem

Where campaign automation stalls

  • A launch calendar lives in a sheet while the publishing happens somewhere else.
  • The webhook fires once, fails quietly and the follow-up email never sends.
  • Nobody can prove which campaign actually reached the network on time.
  • Every channel has a slightly different rule and the checklist grows arms.

What fits

Signals in, posts out

A queue that survives restarts

Scheduling is durable, so a restart does not drop a planned post. The calendar is the source of truth between campaigns.

Retries with backoff on webhooks

A failed publish event retries instead of disappearing, which keeps the downstream steps in your stack in step with reality.

Idempotent writes for batch jobs

A nightly campaign job can retry the same request and get the same post back, so a rerun does not double publish a launch.

Per-platform status for reporting

Read which channels accepted a post and which errored. That is the row your weekly report needs, not a single tick.

Campaign row becomes a scheduled post

POST /public/v1/posts
{ "type": "schedule",
  "date": "2026-11-12T08:00:00Z",
  "posts": [{ "channelId": "{{ campaign.channel }}",
              "content": "{{ campaign.copy }}" }] }

# then subscribe to the publish webhook and write the result
# back into the campaign row as the delivery evidence.

Plan fit

Pricing for a growth team

Team

$35 / month

Ten channels and unlimited seats lets a small growth team plus a contractor share one account without seat arithmetic.

Straight answers

What this is not built for

  • There is no campaign reporting dashboard. Analytics stay per post and per channel.
  • No marketing automation inside the product, so the logic lives in your stack.
  • No comment or DM handling, which means community work stays in another tool.

FAQ

Marketing ops questions

Can I trigger a post from a CRM or a spreadsheet?

Yes. Anything that can send an HTTP request can create a post. The usual pattern is a campaign row that changes state, then a job that reads it and posts.

How do I know a post actually published?

Read the post by id or wait for the publish webhook. A scheduled state is not a published state, and the API keeps them separate so reports stay honest.

Do webhooks include the platform result?

The event carries the post and its outcome, and the post record keeps per-platform status. Fetch the post if you need the individual channel errors.

What is the difference between this and the developer API page?

Same API, different owner. Here the caller is a campaign workflow with a deadline. There the caller is your product code shipping a feature.

Do we need Pro rather than Team?

Team covers ten channels with approvals and unlimited seats. Pro adds thirty channels, an audit log and priority publishing for teams running more campaigns at once.

Let your AI post
to social media for you.

Connect your accounts, add PostSider to your AI and publish your first post in a few minutes.

7-day free trial · 30+ networks · No credit card