HubSpot troubleshooting

"HubSpot rejected the access token (401)"

The token was not copied in full, was rotated, or the private app was deleted.

Fix: in HubSpot open Settings, Integrations, Private apps, select the Quibo app, open the Auth tab and copy the token again (or rotate it). Then open the site page in Quibo, Update credentials, and paste it; the token is verified before it replaces the old one. Tokens start with pat-.

"The private app is missing the content scope (403)"

The app exists but it was created without the CMS content scope, so it cannot read blog settings or write posts.

Fix: open the app, go to the Scopes tab, add CMS: content, click Commit changes. The token stays the same; click Test connection in Quibo to confirm.

"publishing requires blogAuthorId" or "Property blogAuthorId is required"

HubSpot only publishes a post that has a blog author. Quibo sends the Default author from your brand profile, then the author id from the site credentials, then the first author of the account. This error means none of them resolved to an author that exists in HubSpot.

Fix:

1. Check that the account has at least one author under Content, Blog, Blog authors tab.
2. In Quibo open the brand profile and pick a Default author from the dropdown, then click Save brand profile. If the dropdown is empty, click Re-crawl brand on the site page to discover the authors again.
3. As a last resort open the site page, Update credentials, and enter the author id (the long number in the author's URL) as the fallback.

"Create a blog author in HubSpot first"

The account has no blog author at all, so there is nothing to publish under.

Fix: go to Content, Blog, Blog authors, click Create author and enter a name. Then retry the publish; no further changes are needed in Quibo.

Posts publish without the cover, or the cover points to a Quibo URL

The private app lacks the files scope, so the upload to the file manager was refused with a 403. Quibo still publishes the post, using the original image URL as the featured image.

Fix: open the app in HubSpot, Scopes tab, add Files, commit the changes. From the next publish the cover is uploaded to the /quibo folder of the file manager and served from your HubSpot domain.

"slug is already in use"

Another post in the same blog already has that slug (HubSpot enforces unique slugs per blog, drafts included).

Fix: delete or rename the old post in HubSpot, or change the article slug in Quibo before publishing again. Content refreshes never hit this: they update the existing post in place and keep its slug.

The post went to the wrong blog

Accounts with several blogs (for example one per language) have one content group per blog. Quibo uses the blog id you entered when connecting the site, or the first blog of the account when the field was left empty.

Fix: open the site page, Update credentials, and enter the right Blog ID (in HubSpot: Settings, Content, Blog, choose the blog, the id is the long number in the URL). Posts already published can be moved to another blog from the post editor in HubSpot (Settings tab, Blog dropdown).

Multi-language blogs

HubSpot treats each language as a separate blog. Quibo sets the post language from the site's output language, but it does not create language variations or link translations together.

Fix: create one Quibo site per language blog, each with its own blog id, and let each site publish in its own language. If the post language does not match the blog language, HubSpot may show a warning in the editor; the post is still published.

The post is a draft in HubSpot

Quibo creates the post as a draft, then publishes it. If the publish step fails, the error names the post id and the reason (usually one of the author or scope problems above).

Fix: solve the underlying issue, then either publish the draft from the HubSpot editor or delete it and retry from Quibo. Retrying with the draft still there fails with the slug conflict above.

Test connection passes but publish fails

Test connection only checks the token and the content scope. Publishing also needs a blog, an author and (for the cover) the files scope. Read the error message: it names the failing piece.

Still stuck?

Email support@quibo.cc with the organization ID shown in Settings, Account. Business plans get priority routing, with a typical response under 8 business hours.