Publishing

When an article is ready in Temso, publishing sends it to wherever your content lives — a Shopify blog, a Webflow CMS collection, WordPress, or your own system. You set the destination once per project and every publish from then on goes there.

How it works

Article published in Temso
        ↓  Temso sends the article (contract v1)
Your CMS creates the post
        ↓  optional
Confirm back to Temso with the live URL

Temso delivers the article as JSON the moment it publishes. Once your destination accepts the delivery, the publication is marked succeeded in Temso. Sending the live URL back is optional, and only adds the published link to the record.

Destinations

• Zapier — connect in a few clicks and route articles to Shopify, Webflow, WordPress, or any of Zapier's thousands of apps. Best choice if you don't want to write code.
• Webhook — point Temso at any HTTPS URL and handle the payload yourself. Also what you use for Make and other automation tools.
• WordPress — a built-in direct connection, set up under Settings → Integrations.

One destination per project

A project publishes to one place at a time. If a project already has a destination connected and you try to connect another, Temso tells you to disconnect the first one. This keeps it obvious where any given article went.

Scheduling

Scheduled publishes are delivered at the scheduled time, not when they're queued, so the article your CMS receives is the latest version. Draft and live targets both work: a draft publish asks your destination to create an unpublished post, a live publish creates a public one.