# Connect a publishing destination

> Owners add destinations under Settings, Publishing. Pick the platform, connect it, map fields where needed, choose a default mode and test before saving.

Source: https://wavefront.adwave.com/help/publishing/connect-a-destination (updated 2026-10-14)

A destination is a site or tool Wavefront publishes approved work to, such as WordPress, Webflow or Ghost. An owner adds it once under **Settings → Publishing**, tests it, and then owners and editors can publish to it from any approved draft.

## Destinations you can connect

| Kind | Destinations |
| --- | --- |
| Websites and CMSs | [WordPress](/integrations/wordpress), [WordPress.com](/integrations/wordpress-com), [Webflow](/integrations/webflow), [Ghost](/integrations/ghost), [Shopify](/integrations/shopify) blogs, [HubSpot](/integrations/hubspot), [Contentful](/integrations/contentful), [Sanity](/integrations/sanity), [Strapi](/integrations/strapi), [Storyblok](/integrations/storyblok), [Payload](/integrations/payload), [Notion](/integrations/notion), and sites built from a [GitHub](/integrations/github) repository |
| Newsletters (drafts only) | [Mailchimp](/integrations/mailchimp), [Kit](/integrations/kit), [beehiiv](/integrations/beehiiv) |
| Social | [LinkedIn](/integrations/linkedin), [X](/integrations/x), and other networks through [Ayrshare](/integrations/ayrshare) |
| Anything else | A signed [webhook](/integrations/webhook) to your own code, Zapier, Make or n8n, or [export](/integrations/export) as HTML, Markdown or a zip |

The full list, with what each one supports, is on the [integrations page](/integrations). There's no limit on how many destinations a workspace has.

## Add a destination

1. Open **Settings → Publishing** and choose **Add destination**.
2. Under **Choose a destination type**, pick the platform. Each card says what it supports: content kinds, drafts, scheduling, and whether it connects with a sign-in or a token.
3. Fill in **Settings**, such as the site address. Every address must be public and use https.
4. Under **Credentials**, connect:
   - Choose the platform's connect button (for example **Connect with Webflow**) and approve access on the platform, where the platform offers it.
   - Or choose **Enter a token instead** and paste an API key or token from the platform.
5. Fill in **Field mapping** if the platform needs it. For a CMS collection, pick the target and say which of its fields gets the title, body, image and so on.
6. Under **When a publish request doesn't say**, choose the default: **Create a draft**, **Publish live**, or **Publish on the post's calendar date**.
7. Choose **Test connection**. It checks the settings and credentials without changing anything, and tells you which part failed: the settings, the credentials or the connection.
8. Choose **Test and save**. If you need to save without a passing test, use **Save anyway**.

Credentials are stored encrypted and never shown again. The destination now appears in the **Publishing** box on approved drafts.

## Setup notes for common platforms

- **WordPress (self-hosted).** In WordPress, open **Users → Profile → Application Passwords**, add one named "Wavefront", and paste it with your username. The site must use https.
- **WordPress.com.** Enter the site's address and choose **Connect with WordPress.com**. It asks for access to that site only.
- **Webflow.** Connect, load the fields, pick the collection, then map at least the name, slug and a rich-text body field.
- **Ghost.** In Ghost Admin, add a custom integration under **Settings → Integrations** and paste its API URL and Admin API key. New Ghost destinations create drafts by default.
- **Mailchimp, Kit and beehiiv.** Paste an API key. These only ever receive drafts. beehiiv allows this only on its Max and Enterprise plans.

Each [integration page](/integrations) has the details for its platform.

## Edit or remove a destination

Choose **Edit** on a destination to rename it, change settings or the default mode, or replace credentials. Leave a credential empty to keep the stored one. Settings can't change while something is publishing there.

When a platform stops accepting the connection, the destination shows **Reconnect needed**. Open **Edit** and choose **Reconnect**.

Removing a destination keeps the history of what was published there, but nothing new can be published to it.

## Webhook destinations

A webhook destination sends each published article to your https address as a signed JSON request. Give it a name and the URL. Wavefront makes its signing secret and shows it once. **Send test event** sends a signed test and shows the status code. **Rotate secret** makes a new one; for 24 hours both secrets sign each request, unless you choose **Stop signing with the old secret now**.

## IndexNow

Destinations that publish live have an IndexNow switch. When it's on, Wavefront tells Bing and other engines that support IndexNow about each new URL after checking the page.

## Who can set up destinations

Only owners add, edit, test and remove destinations. Owners' AI agents can add webhook destinations and change settings, but never enter credentials: for anything else they send a link for an owner to finish in the web app. API keys with the `destinations` scope can manage destinations too. Every owner gets an email when an agent or key adds a destination or points one at a new address.

## If something goes wrong

- **"Check the credentials".** The token or password was refused. Create a new one on the platform and paste it under **Edit**.
- **"Check the settings".** An address or ID is wrong, or the account can't see it.
- **"The connection failed".** The site didn't answer. Check that it's online and uses https.
- **A publish fails after it worked before.** The token may have expired. Look for **Reconnect needed**.

---

Wavefront by Adwave. https://wavefront.adwave.com/