.gif)
Explore step-by-step solutions to resolve the 'Invalid connection — please reauthorize app' issue in Make (Integromat).
Book a Free Consultation
Stuck on an error? Book a 30-minute call with an engineer and get a direct fix + next steps. No pressure, no commitment.
.png)
.png)
{
"connectionId": "abc123xyz",
"appName": "ExampleService",
"authorization": {
"type": "OAuth2",
"accessToken": "yourAccessTokenHere",
"expiry": "2023-12-31T23:59:59Z"
},
"status": "invalid" // Indicates that the connection is now flagged as invalid
}
If your app keeps breaking, you don’t have to guess why. Talk to an engineer for 30 minutes and walk away with a clear solution — zero obligation.
This issue occurs when the token or key used to authenticate your connection has surpassed its valid duration. In Make (Integromat), credentials are issued with an expiration time to keep your data secure, and when they expire, the connection stops working until you reauthorize.
This happens when access rights previously granted to the app are manually removed or revoked. With Make (Integromat), if the service provider decides to withdraw permissions or if you accidentally modify the access settings, the app loses authorization and needs to be reconnected.
This cause refers to mismatched or wrongly entered authentication details such as API keys, OAuth tokens, or secret keys. Since Make (Integromat) relies on accurate configuration for safe communication between apps, any error in these settings renders the connection invalid.
This issue arises when the permissions granted during the initial setup do not match the necessary scope required by the app. In Make (Integromat), if the app needs broader access than provided, the connection becomes invalid, requiring a reauthorization with the correct scope settings.
This error can occur if the connected service updates or deprecates its API endpoints, altering the expected data format or access requirements. In Make (Integromat), these changes mean that the app’s stored connection details no longer comply with the service's updated API, leading to an invalid state.
This represents the situation where the established connection has been idle for too long, resulting in a session timeout. In Make (Integromat), prolonged inactivity triggers a security measure that automatically ends the session, and reauthorization is needed to resume data exchanges.
```shell
// Sample HTTP request using curl to test your connection
curl --request GET "https://api.example.com/verify" \
--header "Authorization: Bearer YOUR_NEW_ACCESS_TOKEN" \
--header "Content-Type: application/json"
```
Tip: Refresh the existing connection to make sure that the link between Make (Integromat) and the external app is up-to-date, thereby renewing authentication tokens that may have expired.
Tip: Confirm that the app’s permissions in Make (Integromat) include all the necessary scopes, ensuring a smooth and valid connection without missing access rights.
Tip: Delete the current connection and create a new one to clear any potential configuration issues, resulting in a fresh and correctly authorized setup in Make.
Tip: Check that the API key or other credentials used within Make (Integromat) are current and valid, preventing any authorization errors due to outdated or revoked keys.
From startups to enterprises and everything in between, see for yourself our incredible impact.
They do complex work on extremely fast timelines and effectively manage the testing and pre-launch process to deliver the best possible product. I'm extremely impressed with their execution ability.
