Skip to main content

Setup: Named Credential

A Named Credential stores the address — and the sign-in details — of the system you send webhooks to. Your webhook configuration then refers to the Named Credential by name, so secrets are never written into the webhook configuration itself.

Why secrets never go in the config itself​

A webhook configuration (stored on bytenex__Webhook_Config__c) is a normal Salesforce record: other admins can view it, and it can appear in reports or exports. Passwords, tokens, and other secrets must therefore live in the Named Credential, which Salesforce protects, and not in the webhook configuration. The configuration only holds the Named Credential's Developer Name.

Steps​

  1. Go to Setup → Named Credentials.
  2. Click New (or New Named Credential, depending on your org's Setup view).
  3. Enter the base URL of your endpoint — the starting part of the address of the system you are sending webhooks to.
  4. Add the authentication for that system, as required by that system.
  5. Give the Named Credential a clear name and note its Developer Name — you will type this Developer Name into the webhook configuration.
  6. Click Save.

[Screenshot: Named Credentials list in Setup with a new credential created]

Using it in a webhook​

When you create a webhook, select this Named Credential and enter only the relative path of the endpoint (for example /webhooks/v1/lead-listener) as the Endpoint URL. Webhook Studio combines the Named Credential's base URL with that relative path when it sends.


Was this helpful? Let us know by email — we read every message.