Publish & grow
Publish articles and newsletter drafts
Connect WordPress, Ghost, Dev.to, Hashnode, Beehiiv, Buttondown, Kit, or Listmonk and review destination-specific article and email settings.
Updated
Prepare the destination's API credentials
Open Connections and use the card for your publishing service. Keep credentials private and create a dedicated integration credential when the service supports it. Verify the displayed site, publication, or newsletter before using the connection.
| Service | Credential and context |
|---|---|
| WordPress | Site URL, username, and an Application Password. The site's REST API must be accessible. |
| Ghost | Site URL and the Admin API key from a custom integration. |
| Dev.to | A DEV Community API key. |
| Hashnode | A personal access token and the publication's domain. The publication must have API access. |
| Beehiiv | API key and publication ID. Creating posts through its API requires eligible provider access. |
| Buttondown | The newsletter's API key. |
| Kit | A v4 API key. |
| Listmonk | Server URL, API user, and key. The server must be reachable over HTTPS. |
Review an article before sending it
- Create the content for the connected destination and open its review card.
- Set the title and any offered article fields. Dev.to supports up to four tags; Hashnode has its own tag choices.
- Inspect how the first image is used. WordPress and Ghost use it as the featured image, while Dev.to and Hashnode use it as the cover.
- Choose the destination's draft or publish behavior where offered.
- After the send completes, open the article on the destination and check formatting, images, links, and the publication state.
A short social caption rarely makes a complete article. Add the context, evidence, and steps a reader needs without relying on an image to carry the entire explanation.
Fix provider access and formatting problems
- Authorization refused? Confirm that the key is for the correct API version and has the required access.
- Site unreachable? Check the public HTTPS address, REST API availability, and any access restrictions at the host.
- Provider plan restriction? Check that service's API entitlement. A Krevaya plan cannot grant API access the destination withholds.
- Draft created but no email received? Inspect the destination's draft/send setting before retrying.
- Wrong title, tags, or body formatting? Correct the destination-specific details and inspect a draft in the service before sending another campaign.