https://systematic.workato.com/t5/workato-embedded-discussion/embedded-recipe-shows-quot-connector-not-authorized-quot-even/m-p/10294#M144 <P>Hi everyone!</P><P>I am embedding Workato recipes into a partner portal using the Embedded SDK. Everything works great until a user links their app account (like Salesforce or Slack); but then immediately sees a “Connector not authorized” error when trying to run the recipe. <span class="lia-unicode-emoji" title=":thinking_face:">🤔</span>The account <EM>is</EM> showing as connected in the connections tab &amp; manually testing from within the platform works fine.</P><P data-unlink="true">This seems to happen only when the connector is authorized through the embedded UI;&nbsp;not when it's pre-linked via the main Workato interface. <span class="lia-unicode-emoji" title=":smiling_face_with_smiling_eyes:">😊</span>It’s like the embedded experience is missing a final handshake / permission sync after OAuth completes. Refreshing the session /re-adding the connection sometimes helps but it’s not reliable. Checked&nbsp;<A href="https://docs.workato.com/en/oem/embedded-connections.html" target="_self">https://docs.workato.com/oem/embedded-connections.html-</A><A href="https://www.igmguru.com/digital-marketing-programming/ruby-on-rails-certification-training" target="_self">Rails course&nbsp;</A>guide related to this and found it helpful.&nbsp;</P><P>Is there a known solution or callback step to ensure embedded connectors become immediately valid after linking?<span class="lia-unicode-emoji" title=":thinking_face:">🤔</span> Any tips on debugging connector state within the embedded context would be super helpful!</P><P>&nbsp;</P><P>&nbsp;</P><P>Thank you !!<span class="lia-unicode-emoji" title=":smiling_face_with_smiling_eyes:">😊</span></P> Tue, 24 Jun 2025 04:34:23 GMT gabrielladawn 2025-06-24T04:34:23Z https://systematic.workato.com/t5/workato-embedded-discussion/embedded-recipe-shows-quot-connector-not-authorized-quot-even/m-p/10294#M144 <P>Hi everyone!</P><P>I am embedding Workato recipes into a partner portal using the Embedded SDK. Everything works great until a user links their app account (like Salesforce or Slack); but then immediately sees a “Connector not authorized” error when trying to run the recipe. <span class="lia-unicode-emoji" title=":thinking_face:">🤔</span>The account <EM>is</EM> showing as connected in the connections tab &amp; manually testing from within the platform works fine.</P><P data-unlink="true">This seems to happen only when the connector is authorized through the embedded UI;&nbsp;not when it's pre-linked via the main Workato interface. <span class="lia-unicode-emoji" title=":smiling_face_with_smiling_eyes:">😊</span>It’s like the embedded experience is missing a final handshake / permission sync after OAuth completes. Refreshing the session /re-adding the connection sometimes helps but it’s not reliable. Checked&nbsp;<A href="https://docs.workato.com/en/oem/embedded-connections.html" target="_self">https://docs.workato.com/oem/embedded-connections.html-</A><A href="https://www.igmguru.com/digital-marketing-programming/ruby-on-rails-certification-training" target="_self">Rails course&nbsp;</A>guide related to this and found it helpful.&nbsp;</P><P>Is there a known solution or callback step to ensure embedded connectors become immediately valid after linking?<span class="lia-unicode-emoji" title=":thinking_face:">🤔</span> Any tips on debugging connector state within the embedded context would be super helpful!</P><P>&nbsp;</P><P>&nbsp;</P><P>Thank you !!<span class="lia-unicode-emoji" title=":smiling_face_with_smiling_eyes:">😊</span></P> Tue, 24 Jun 2025 04:34:23 GMT https://systematic.workato.com/t5/workato-embedded-discussion/embedded-recipe-shows-quot-connector-not-authorized-quot-even/m-p/10294#M144 gabrielladawn 2025-06-24T04:34:23Z