Issues with Hootsuite app connection expiring

Hi ​@jreiddossinger 

Check the Hootsuite Status page for recent/ongoing incidents: https://status.hootsuite.com/

You can try opening a ticket with Zapier Support: https://zapier.com/app/get-help

Hi ​@jreiddossinger 👋 How are things going on this, are the Hootsuite connections still expiring?

I couldn't see any recent incidents for Hootsuite that appeared to be related. But if Hootsuite changed how their API handles authentication, that could be affecting how the app integration refreshes auth tokens, which might explain why connections are expiring so quickly. Like Troy suggested, I’d recommend contacting our Support team so they can investigate this further.

Keep us posted on how you get on with them!

Thanks, all. I’ve been in touch with Zapier support, who are very helpful, but still have no resolution to the issue. I’m going to Hootsuite support. If I find a solution, I’ll post it here.

In the meantime, I would still be curious if anyone else has found this issue. As far as I can tell, it’s just my account.

Sorry to hear it's still unresolved ​@jreiddossinger. Hopefully Hootsuite's support team can help get to the bottom of it. Appreciate you keeping us in the loop! 

A consistent ~15-minute expiry is a useful clue: it usually points to the access token expiring while the refresh-token exchange is failing, not a random connector outage.

A clean diagnostic sequence would be:

1. Revoke every existing Zapier authorization from Hootsuite’s connected-app settings.
2. Remove the stale Hootsuite connections in Zapier, then authorize one fresh connection only.
3. Test immediately and again after 20 minutes.
4. Record the exact test times, connection ID/name, and any error/correlation ID (no tokens or account identifiers).
5. If it expires again, give those timestamps to both support teams and ask specifically whether the OAuth refresh request is rejected, the refresh token is missing, or scopes changed after Hootsuite’s platform update.

I would avoid repeatedly creating parallel connections because it can leave multiple grants and make the signal harder to interpret. Also keep affected Zaps paused or add a failure route until refresh is reliable, so failed social actions are queued rather than silently lost.

We use the same token-lifecycle checks in Atlantic’s integrations because “connect succeeded” only proves the initial exchange, not refresh behavior. I’m Ege, co-founder of Atlantic, sharing our integration-debugging pattern rather than an official Hootsuite diagnosis.