Integrations & API

Schedule posts from the tools you already use

Connect Kadenzo to Zapier, Make, and Pipedream with no code — or call the API directly with a key you generate in seconds. Trigger a scheduled post from anywhere, and it publishes through each network's official API, exactly like a post you made by hand.

Get your API keySee how it works
When this happensTrigger
“Launch teaser 🚀”
New row added · publish Tue 9:00 AM
from any of your tools
Zapier · Make · API
Scheduled in Kadenzo
Tuesday · 9:00 AM
Queued
Launch teaser 🚀 — here’s what’s new this week…
Goes live on

How it works

Four steps from idea to live — and the last one runs without you.

Step 1

Generate a key in your settings

Open Settings → API keys, name one ("Zapier", "Our CMS"), and copy it once. It's shown a single time and stored hashed — revoke it any moment and it stops working instantly, no effect on your account.

API keys
kdz_live_…a1b2 · Zapier
kdz_live_…7f9c · Our CMS
Revoke any time
Step 2

Wire a trigger — no code needed

In Zapier, Make, or Pipedream, pick the event that should kick things off — a new row in a sheet, an approved draft in Notion, a fresh blog post — and connect it to Kadenzo with the key. No glue code, no server to host.

When this happens
→New row in Google Sheets
→Post approved in Notion
✓Schedule in Kadenzo
Step 3

Or call the API directly

Prefer your own code? POST to /api/v1/posts with the content, the accounts, and a future time. Kadenzo validates the accounts are yours, ingests any media, and queues the post — one endpoint, the same checks the composer runs.

POST /api/v1/posts
201 Created
status: pending
Jul 1 · 9:00 AM
scheduled_for
2 accounts
X · LinkedIn
Step 4

It publishes itself, safely

At the scheduled minute the post goes live through each network's official API — the same pipeline as a post you scheduled by hand. No password sharing, no scraping, nothing posts that you didn't queue.

Published
X · live 9:00 AM
LinkedIn · live 9:00 AM
Official APIs only

What you get

No-code, with Zapier & Make

Connect Kadenzo to thousands of apps through Zapier, Make, and Pipedream. Wire the trigger once and posts schedule themselves — no developer, no maintenance.

A clean API when you want it

One documented endpoint, key authentication, JSON in and out. Schedule straight from your own systems with the same validation the in-app composer uses.

Keys you control

Generate as many as you need, label them per tool, see when each was last used, and revoke any one instantly. Keys are stored hashed and shown in full only once.

Official-API publishing underneath

Posts pushed in by API publish exactly like in-app ones — through each network's own API, never scraping or password sharing. The safety story doesn't change.

Built for agencies and ops

Push a month of a client's calendar from your own pipeline, or let a content engine feed the queue — without anyone opening the composer by hand.

Your accounts, your rules

Every API post is checked against the accounts you've connected and your plan's limits before it's queued — the API can't touch a channel you don't own.

Most of the work happens before the post

Scheduling a post is the visible part. The invisible part is everything that feeds it: the spreadsheet your team drops ideas into, the CMS that publishes the blog you want to announce, the approval that finally lands in your project tool. Today most teams bridge that gap by hand — someone watches for the trigger and copies the content into the scheduler.

That's the manual work Kadenzo's integrations remove. Connect it to Zapier, Make, or Pipedream and the bridge runs itself: an approved draft becomes a scheduled post, a new product becomes a launch thread, a published article becomes a week of promotion — with no one tabbing between tools to make it happen.

It's the same promise as the rest of Kadenzo, pushed one step earlier in your workflow. The post still goes out on time through official APIs; you just stop being the wire between your systems and your calendar.

Stop being the wire between your other tools and your posting calendar.

Kadenzo vs Copying it in by hand

Kadenzo
Copying it in by hand
Schedule from another tool automatically
No-code setup (Zapier / Make / Pipedream)
Direct REST API with your own key
Publishes through official platform APIs
Still manual
Can't post to accounts you don't own
Up to whoever's copying
Runs while you're asleep
Pull analytics back out by API
Not yet

Who it's for

Sheet to schedule

Keep planning posts in the spreadsheet your team already loves. A new row triggers a scheduled Kadenzo post automatically — no re-typing, no copy-paste window.

Solo creators

A client's calendar from your own pipeline

Generate a month of a client's posts in your internal tool and push them all into Kadenzo by API — then manage and adjust them on the calendar like any other post.

Agencies

Announce whatever you ship

Wire your CMS or release tool to Kadenzo so every new article or launch fans out into a scheduled cross-network post the moment it goes live.

In-house teams

Frequently asked

Do I need to be a developer to use this?

No. The most common way to use it is no-code: connect Kadenzo to Zapier, Make, or Pipedream, pick a trigger, and posts schedule themselves. The direct REST API is there if you'd rather write the integration yourself, but it's optional.

What can the API actually do?

It schedules a post: you send the content, which of your connected accounts to use, a future time, and optionally media URLs or per-network overrides. Kadenzo validates it and queues it, then publishes it through each network's official API at the set minute. It's schedule-only in v1 — no instant publish and no draft mode.

Can I read analytics or pull data out by API?

Not yet. Version 1 is focused on getting posts in, not pulling numbers out, so there are no read or analytics endpoints today. If that's what you need, the in-app analytics dashboard and its PDF/CSV exports cover it for now.

How does authentication work?

Generate an API key in Settings → API keys. It's shown once and stored hashed, so copy it when you create it. Send it as a Bearer token on each request. You can name keys per tool, see when each was last used, and revoke any one instantly without affecting your account.

Is it safe to let another tool post for me?

Yes, within tight limits. A key can only schedule posts to accounts you've already connected and only within your plan's limits — it can't reach a channel you don't own, and everything still publishes through official platform APIs. Revoke the key any time and it stops working immediately.

Which plans include API access?

Professional and Enterprise. It's part of the same plans that unlock the heavier automation features, so the teams most likely to wire Kadenzo into their stack already have it.

Works well with

Multi-Platform PublishingWhere every API-scheduled post actually goes out.Posting QueueLet pushed-in posts fill your best slots automatically.Content CalendarManage and adjust API posts alongside everything else.

Schedule from the tools you already use.

Put api & integrations to work in your calendar — start a free 7-day trial, cancel anytime.

Start your 7-day trial