Authenticate a Custom Webhook with OAuth2

The Custom Webhook action can sign in to another service using OAuth2, the same secure sign-in method many large platforms use. This lets a workflow call services such as Google or social networks without storing passwords in the request.

Choose OAuth2 in the action

1. Add a Custom Webhook action to your workflow.
2. Set the method and the destination address as usual.
3. In the Authorization section, choose OAuth2.
4. Pick an existing saved token, or request a new one and approve access when the other service asks.
5. Save the action.

Manage saved tokens

Tokens are collected in one place so you can maintain them without opening each workflow.

1. Go to Automation > Global Workflow Settings.
2. Find the Manage Tokens section and click Manage Token.
3. A window lists all tokens. Use Update to refresh one, or Delete to remove one you no longer want.

When this is useful

• The service you are calling does not accept a simple API key.
• You want access granted by a person's account with limited permissions rather than a shared password.
• Several workflows need the same connection and you want to renew it once.

Troubleshooting

If a webhook suddenly fails with an authorization error, the token may have expired or been revoked. Update it from Manage Token and run the action again.

Good to know: Give tokens clear names after approving them so you can tell which service and account each one belongs to.