How to Use OAuth2 in a Sparkforge Custom Webhook

By Sparkforge Support Team ·Last reviewed May 3, 2026

Custom Webhook actions support OAuth2 authorization for connecting to Google, Facebook, LinkedIn, and similar APIs. Tokens are managed centrally under Global Workflow Settings.

OAuth2 is the standard authorization method for large APIs like Google, Facebook, and LinkedIn. The Custom Webhook workflow action supports OAuth2, so you can hit those APIs from a workflow without building a separate integration.

How to authenticate a Custom Webhook with OAuth2

  1. In the workflow, add a Custom Webhook action.
  2. Set the authorization option to OAuth2.
  3. Pick an existing token, or request a new one and complete the consent flow with the third-party API.
  4. Configure the rest of the webhook (URL, method, headers, body) and save.

Manage OAuth2 tokens

  1. Open Global Workflow Settings.
  2. Find the Manage Tokens section.
  3. Click Manage Token to open the full token list.
  4. Update or delete tokens as needed.

Frequently Asked Questions

Why use OAuth2 instead of an API key in a Custom Webhook?
OAuth2 is the standard for large APIs like Google, Facebook, and LinkedIn. Many services either require it or expose more functionality through it than through API keys alone.
Where do I manage OAuth2 tokens?
Open Global Workflow Settings and click Manage Tokens. The list shows every token in the account; you can update or delete any of them.
Can multiple webhooks share one token?
Yes. Once a token exists, any Custom Webhook in your workflows can pick it from the existing token list.

Was this article helpful?

Related Articles