Could not connect to mattermost account on Zapier

I tried to connect the Mattermost account on Zapier, all steps followed as described here.

it’s asking for access to Mattermost as well and it gets connected for a second and then it again shows the error as shown in the screenshot attached. please help me resolve this issue.
connecting via OAuth2.0 application.

Hi Ayesha! Lets get this fixed for ya ASAP. For starters, I’d recommend double-checking your OAuth 2.0 setup as outlined in our Zapier integration guide and ensuring all permissions are correctly configured. If the issue persists, let us know so we can help you further troubleshoot!

Hi John
yes, i made sure all the permissions were correctly configured and did OAuth 2.0 setup as per the integration guide, and tried again and again, but the issue persists. can you specify any particular permission that I need to configure to set it out?

Hi Ayesha! Thanks for double-checking the permissions and OAuth setup. In some cases, issues like this can arise if the ‘trust remote code’ setting for OAuth 2.0 is not fully enabled or if the Mattermost account lacks specific admin permissions. Additionally, make sure the app you’re using in Zapier has the necessary permissions to access channels and post messages as intended.

Hey @john.combs,

Sorry for necrobumping this thread, but I’m facing the exact same issue.

After triple-checking OAuth params and re-creating the App in Zapier at least ten times, it still fails to connect.

Zapier’s API (/graphql endpoint, "operationName": "TestAuths") gets the following response from our MM.

The app returned "Sorry, we could not find the page.".

Not quite sure where to go from here - could you please help?

Cheers

If a solution doesn’t turn up here, you could open an issue in the repo: GitHub · Where software is built

1 Like

Thanks @john.oliver, I’ll give it a few more days, but will make sure to create an issue if nobody could help.

1 Like

@aberenyi v1.11.0 of the Zapier integration was just released… maybe that’ll help!

1 Like

Cheers @john.oliver, the new version indeed fixed the issue, thanks for letting me know!

Btw, how did you you realise that there is a new version available?

2 Likes

Terrific! I saw an internal announcement.

1 Like