OAuth Issue with Clay Sequencer Installation via Entra ID

Alexis L. · 2026-01-12T11:20:21.359Z

Hi Clay team 👋 We’re trying to install Clay Sequencer for a client via Microsoft Entra ID and are hitting an OAuth issue. Error on our side: Microsoft: “App launch failed” • Clay callback: “Could not generate OAuth code and state” App ID: 706054db-778d-4fee-bb14-ffc5a7c7f096 Correlation ID: ae8eb1c4-ecd4-4bd8-8a9b-a4dc6b87e9eb Timestamp: 2026-01-12T11:12:58Z We’ve double-checked redirect URI, admin consent, user assignment, and permissions in Entra ID. Could you confirm if anything is required on the Clay side? Has this issue ever ocurred before ? Thanks!

OAuth Issue with Clay Sequencer Installation via Entra ID | Clay

12 comments

· Sorted by Oldest

Clay Support
APP
·
·
This OAuth error with Microsoft Entra ID is a known issue that can occur during the admin consent process for Clay Sequencer. The "Could not generate OAuth code and state" error typically happens when there's a timing or configuration mismatch during the OAuth flow. [1]
Since you've already verified the redirect URI, admin consent, user assignment, and permissions in Entra ID, the issue might be on our side or related to the OAuth flow timing.
Before I connect you with our team for deeper troubleshooting, I'd recommend trying our built-in AI tool called Sculptor (available in the top-right corner of your Clay workspace). Sculptor can help you set up automations and might provide additional guidance for OAuth configurations.
If Sculptor doesn't resolve this, please let me know and I'll connect you with a human teammate who can investigate the specific OAuth callback error and work with you on the Microsoft Entra ID integration.
Clay Support
APP
·
·
Is that what you were looking for?
Alexis L.
·
·
sculptor can deal with auth issues ?
Clay Support
APP
·
·
Yes, Sculptor can help with authentication issues! It can guide you through authentication problems, body formatting issues, and other API configuration challenges. [1]
You can paste error messages into Sculptor for suggested fixes and get help interpreting unexpected responses. [2] However, for your specific Microsoft Entra ID OAuth issue with Clay Sequencer, this might be beyond what Sculptor can resolve since it's a deeper integration problem.
Give it a try first - if Sculptor can't help with this particular OAuth callback error, let me know and I'll connect you with a human teammate.
Clay Support
APP
·
·
Did that answer your question?
Alexis L.
·
·
connect to team please
Clay Support
APP
·
·
Got it — I’m connecting you to a human teammate now.
Clay Support
APP
·
·
Our support team has got your message and we'll get back to you soon! We're currently outside of our standard office hours (9 AM to 9 PM EST, Monday through Friday), so it may take a little longer for us to respond.

If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!

image.png(93 kB)
Aditi S.
·
·
Hi Alexis - thanks so much for reaching out. From what I can see, it seems like you're completing Microsoft’s admin consent flow. Admin consent only approves the Clay app for the tenant - it does not connect an email account and does not return OAuth code / state values, which is why Clay shows that message.
What to do next:
1.
If admin consent was just completed, wait up to 24 hours.
2.
Then go to Clay Sequencer → Sender Setup
3.
Click Add email accounts → Microsoft Outlook (OAuth) This is the step that actually connects the mailbox and should work
Let us know if it still doesn’t work after trying the “Add email accounts” flow.
Aditi S.
·
·
Just a quick follow up on this: Admin consent only approves permissions - the actual mailbox owner still needs to sign in once. Please go back to Clay, then reconnect and complete the Microsoft login as the inbox user (not just as an admin).
Alexis L.
·
·
Aditi S. this is very clear but the error happens on first admin step. Your answer suggests we stopped during the identification process, it's not the case. Please study the error more closely and if you are able to identify it please let me know.
Kashif J.
·
·
Hi Alexis, Were you still experiencing the above bug after waiting a little after establishing the admin consent? If yes, I can escalate this and have the engineering team look at it.

Clay Support
APP
·
·
This OAuth error with Microsoft Entra ID is a known issue that can occur during the admin consent process for Clay Sequencer. The "Could not generate OAuth code and state" error typically happens when there's a timing or configuration mismatch during the OAuth flow. [1]
Since you've already verified the redirect URI, admin consent, user assignment, and permissions in Entra ID, the issue might be on our side or related to the OAuth flow timing.
Before I connect you with our team for deeper troubleshooting, I'd recommend trying our built-in AI tool called Sculptor (available in the top-right corner of your Clay workspace). Sculptor can help you set up automations and might provide additional guidance for OAuth configurations.
If Sculptor doesn't resolve this, please let me know and I'll connect you with a human teammate who can investigate the specific OAuth callback error and work with you on the Microsoft Entra ID integration.
Clay Support
APP
·
·
Is that what you were looking for?
Alexis L.
·
·
sculptor can deal with auth issues ?
Clay Support
APP
·
·
Yes, Sculptor can help with authentication issues! It can guide you through authentication problems, body formatting issues, and other API configuration challenges. [1]
You can paste error messages into Sculptor for suggested fixes and get help interpreting unexpected responses. [2] However, for your specific Microsoft Entra ID OAuth issue with Clay Sequencer, this might be beyond what Sculptor can resolve since it's a deeper integration problem.
Give it a try first - if Sculptor can't help with this particular OAuth callback error, let me know and I'll connect you with a human teammate.
Clay Support
APP
·
·
Did that answer your question?
Alexis L.
·
·
connect to team please
Clay Support
APP
·
·
Got it — I’m connecting you to a human teammate now.
Clay Support
APP
·
·
Our support team has got your message and we'll get back to you soon! We're currently outside of our standard office hours (9 AM to 9 PM EST, Monday through Friday), so it may take a little longer for us to respond.

If you’re dealing with a specific table, drop the URL below so we can help you quicker. Otherwise, someone from our team will be in touch soon!

image.png(93 kB)
Aditi S.
·
·
Hi Alexis - thanks so much for reaching out. From what I can see, it seems like you're completing Microsoft’s admin consent flow. Admin consent only approves the Clay app for the tenant - it does not connect an email account and does not return OAuth code / state values, which is why Clay shows that message.
What to do next:
1.
If admin consent was just completed, wait up to 24 hours.
2.
Then go to Clay Sequencer → Sender Setup
3.
Click Add email accounts → Microsoft Outlook (OAuth) This is the step that actually connects the mailbox and should work
Let us know if it still doesn’t work after trying the “Add email accounts” flow.
Aditi S.
·
·
Just a quick follow up on this: Admin consent only approves permissions - the actual mailbox owner still needs to sign in once. Please go back to Clay, then reconnect and complete the Microsoft login as the inbox user (not just as an admin).
Alexis L.
·
·
Aditi S. this is very clear but the error happens on first admin step. Your answer suggests we stopped during the identification process, it's not the case. Please study the error more closely and if you are able to identify it please let me know.
Kashif J.
·
·
Hi Alexis, Were you still experiencing the above bug after waiting a little after establishing the admin consent? If yes, I can escalate this and have the engineering team look at it.