Skip to main content

Webhook Templates

Webhook Templates are reusable webhook requests - URL, method, headers, authentication and body, saved once and used in any webhook campaign or journey step. A typical one is "Send MMS via Delivyr": every journey that needs it reuses the same request instead of re-typing it. They live in Brand Studio → Webhook Templates (/brand/webhook-templates). Viewing the library requires templates:read; creating and editing require templates:write.

What a webhook template holds​

The full request the webhook step sends: the URL, the HTTP method, custom headers, authentication (none, bearer token, basic, API key header, or HMAC signing), and the body - JSON with Liquid placeholders such as {{user.phone}}, or form-encoded fields. The builder is the same form as the campaign webhook step, including Send a test against a sample contact. The test uses the contact you pick - a real contact is rendered exactly as a live send would render it - and the result switches between Response received and Request sent, the exact method, URL, headers and body that went out, with credentials masked.

Secrets​

Tokens, passwords, API keys and signing secrets are encrypted when a template is saved and never shown again: a saved secret appears as a masked field. Leave the masked field as it is to keep the secret, clear it to remove it, or type a new value to replace it. A test send never transmits a masked value; re-enter the secret if you want to test it.

When a campaign or journey is built from a template, Joryio copies the template's stored secret into the copy on the server, so the message carries the credential without the secret ever passing through your browser.

Using a template​

  • Campaigns - on the webhook compose step a new message opens on two tiles: Build the request or Use a webhook template. Pick a template by name (most recently edited first) and it is copied into the message.
  • Journeys - a webhook Message node, and the standalone Webhook block, have a Start from template search at the top of the request tab.

The campaign or journey owns the copy. Editing it, or editing the template later, never affects the other. Deleting a template is safe: existing copies keep working.

Managing templates​

The library lists each template with its method and URL, who created and last edited it, and when. Rows offer Edit, Duplicate and Delete; selecting rows opens a bulk delete. Search matches the name, description and URL; the tag filter narrows by tag.