# Automation with connector in oAuth2 user authentification

**URL:** <https://community.tulip.co/t/automation-with-connector-in-oauth2-user-authentification/15890>\
**Category:** Product Suggestions\
**Tags:** automations\
**Created:** [November 28, 2025, 3:19pm UTC](https://community.tulip.co/t/automation-with-connector-in-oauth2-user-authentification/15890 "2025-11-28T15:19:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nicolas](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/nicolas/32/3349_2.png) [@Nicolas](https://community.tulip.co/u/Nicolas)\
**Post date:** [November 28, 2025, 3:19pm UTC](https://community.tulip.co/t/automation-with-connector-in-oauth2-user-authentification/15890/1 "2025-11-28T15:19:22Z")

</div>

Today, most our apps are integrated with our backend SAP, with API call in synchronous way.  
Each step/action run couple of api call (sometime +5/10) that lead performance complain from operator that need to wait +2-5 seconds.  
Moreover SAP API could fail due to blocking objet in SAP, some retry loop and wait trigger is in place in Tulip apps but that degrade performance and operator usability.

One approach to improve drastically apps performance would be asynchronous integration and Tulip automation would be perfect.  
Api will be call in asynchronous way, we could orchestrate api calls (remove complexitiy in app triggers), implement retry logic and reuse automation cross multiple apps.  
However integration with SAP is in oAuth2 user authentification and today not supported by Automation.  
It will be great if Automation could support oAuth2. Ideally trigger from the apps and take end-user context with oAuth2 token.

Huge business value for us.

---

<div class="post-metadata">

**Author:** ![Nicolas](https://sea2.discourse-cdn.com/flex020/user_avatar/community.tulip.co/nicolas/32/3349_2.png) [@Nicolas](https://community.tulip.co/u/Nicolas)\
**Post date:** [March 26, 2026, 8:55am UTC](https://community.tulip.co/t/automation-with-connector-in-oauth2-user-authentification/15890/2 "2026-03-26T08:55:18Z")

</div>

Internally we have investigating this topics.

Backend process (like automation) for Front end is now commun integration pattern.  
One way for backend proecess API call “on-behalft” of a user is to use the standard oAuth2 exchange token process.  
We have explore the usage of “oAuth Token exchange” in Tulip connector, but unformatly we don’t have access to user access token.  
Could you explore this feature of using “oAuth Exchange token” flow?