Journeys HTTP action authentication (e.g. oAuth2)

Business problem

Teams are currently limited when automating workflows that require integration with external CRMs or internal tools because HTTP actions lack native authentication support. Manually configuring headers for APIs requiring OAuth2, Bearer tokens, or API keys is complex and often impossible, preventing the use of many modern third-party services.

Wished result

Workflow HTTP actions should include built-in support for standard authentication methods like OAuth2, Basic Auth, and API keys. These credentials should be securely stored and reusable across different workflows, with automatic token refresh handling to ensure integrations remain functional without manual intervention.