Back to Changelog
New

Journeys HTTP action authentication (e.g. oAuth2)

HTTP Actions within Journeys now support native authentication methods, streamlining integrations for everyone using them to automate workflows.

What's new

  • Integrated support for OAuth2, Basic Auth, and API Key authentication in HTTP Actions.

  • Automatic token refresh ensures continuous integration with external services.

Why this matters

You can now connect Journeys to a much wider array of external CRMs and internal tools without wrestling with manual header configurations. This simplifies integration setup and maintains reliable data exchange, freeing your team from integration headaches.