Publish to WordPress from Growth Calendar

Finished articles can go to WordPress without any copying and pasting. Send them one at a time, have every finished article arrive as a draft, or let them publish themselves.

There is one setting for the whole workspace, under CMS in the top right of Growth Calendar.

What you need

WordPress needs an application password. Your normal login password will not work.

In WordPress, open Users > Profile.
Under Application Passwords, enter a name such as Timothe and select Add New Application Password.
Copy the string it shows you. It is never displayed again.

Create it on a user with Editor or Administrator rights. An account that cannot publish will be refused at connect time.

Connecting

Open CMS in the top right of Growth Calendar.
Enter the site URL (https://example.com), the username, and the application password.
Select Connect.

Connecting checks the site straight away to confirm it can accept posts. If it reports a problem, see "When it does not work" below.

For a site installed in a subdirectory (https://example.com/blog), enter that address as it is.

Choosing how articles are sent

Once connected, the same screen offers three choices.

Setting	What happens
Manual	Nothing is sent automatically. Articles go only when you select "Publish to CMS".
Send as draft	Every finished article arrives in WordPress as a draft for you to review.
Publish automatically	Every finished article goes live as soon as it is written.

The default is Manual. Starting with manual or drafts and switching to automatic publishing once you trust the output is the safer path.

Setting a category and an author applies them to everything that gets sent. Both are read from the connected site, so there are no numeric ids to look up.

Sending a single article

Use Publish to CMS at the top right of an article. The control next to it switches between sending as a draft and publishing immediately.

Sending the same article twice updates the existing WordPress post rather than creating a second one, so revising and re-sending never leaves duplicates behind.

About internal links

Growth Calendar links articles in the same cluster to each other. When an article is sent, links to siblings that have already been sent become their real URLs.

Links to articles that have not been sent yet are unwrapped to plain text. A link to an address that does not exist would send readers to an error page. Work through a cluster in order and each article will link correctly to the ones before it.

About images

Images inside an article keep their Timothe-hosted addresses. They are not copied into the WordPress media library.

When it does not work

"WordPress did not accept the credentials"

There are three possible causes:

The username or application password is wrong.
The server is not passing credentials through to WordPress. Some hosts strip the Authorization header and need it forwarded in .htaccess.
The site is not served over HTTPS. Application passwords only work on HTTPS sites.

"That address did not return the WordPress REST API"

The site's Settings > Permalinks is probably set to Plain. Change it to Post name, or any option other than Plain, and try again.

"No WordPress REST API at that address"

A security plugin may be blocking the REST API. Allow REST API access in its settings. A mistyped site URL produces the same message.

"That WordPress user cannot manage posts"

That user has no publishing rights. Create the application password on an Editor or Administrator account instead.

Other CMSs

WordPress, Ghost and Shopify are supported today. Other systems will connect from the same screen as they are added.