Advanced settings

The Advanced Settings allow you to extend the functionality of your forms by deciding what happens after a submission, managing data delivery, and adding custom metadata.

In this section, you can:

• Set the Success action. Show an inline success message or send visitors to another URL (redirect) once they submit the form.

• Attach Webhooks. Automatically send form data to external services after submission.

• Custom Key-Value Configs. Add custom configuration values that are included in the form data payload.

The Success action group sits at the top of your form's Settings tab. It controls what a visitor gets once Branchside has accepted their submission.

Forms keep the Message behavior until you change it.

To redirect visitors after a submission:

1. Edit your form and click the Settings tab.

2. In the Success action group, select Redirect.

3. Enter the destination in the Redirect URL field. Use the complete address, including http:// or https://.

4. Save the form, then submit it once to confirm the destination opens.

Note: Only plain web addresses work. Links starting with javascript:, mailto: or tel:, and addresses without a scheme (example.com/thank-you) are refused when you save the form.

You can pass the value a visitor just submitted into the destination URL by wrapping the field name in curly braces — for example {first_name}.

• A placeholder uses the field's name (not label), the same value you use for pre-filling fields.

• While you set the URL, the helper text underneath shows every placeholder your current form offers.

• When a placeholder appears more than once, every occurrence is replaced.

• Submitted values are encoded automatically, so John Doe becomes John%20Doe and [email protected] becomes john%40example.com.

• Checkbox selections are joined with a comma, so two picked interests arrive as sports%2Cmusic.

• Consent checkboxes and hidden fields have names like any other field, so they can be used as placeholders.

Examples:

If a name in the URL does not match a field on the form, or the visitor left an optional field blank, the placeholder resolves to an empty value instead of failing. A typo such as {fist_name} quietly produces ?name=. Check the helper text, then test the form with a real submission before you send traffic to it.

• It happens in the browser. The destination is opened by the visitor's browser once the submission is accepted; it is not a server-side redirect.

• Tracking fires first. Conversion events configured on the form are recorded before the browser navigates away, a brief moment (about half a second) after the successful submission.

• JavaScript is required. Because the form script performs the redirect, visitors with JavaScript disabled stay on the inline success message instead.

• Only submitted values are available. Placeholders resolve from the data the visitor just sent. To forward UTM data, capture it into hidden fields first, then use those field names as placeholders.

• Simple symbols only. A field name may contain letters, numbers, underscores, hyphens, and dots (so {user.name} works), and nothing else: no default values, filters, or expressions.

1. Edit your form and click the Settings tab.

2. Click the Advanced settings button to open the configuration menu.

To manage webhooks, select the Webhooks tab within the Advanced Settings menu. From here, you can select and attach available webhooks to your form.

Note: If no webhooks are listed, you must create them first. For more information, see the Webhooks documentation.

The Config tab allows you to define custom key-value pairs that will be included in every form submission. This is particularly useful for passing static metadata to your integrations.

• Nested Keys: You can use dot notation (e.g., webhook.extra_field) to create nested objects in the payload.
• Storage: These values are included in the form.config object within the JSON payload.

Payload example with config:

{
  "form": {
    "type": "base",
    "id": "e7994b79-2a1d-4978-8c5a-94d95556b5b2",
    "name": "Demo form",
    "config": {
      "custom_name": "Custom form name for my integration",
      "webhook": {
        "extra": "Config key for this nested object is `webhook.extra`"
      }
    },
    "fields": {
      "user.name": {
        "type": "text",
        "name": "user.name",
        "label": "User name"
      },
      "user.email": {
        "type": "text",
        "name": "user.email",
        "label": "User email"
      }
    }
  },
  "data": {
    "user.name": "demouser",
    "user.email": "[email protected]"
  },
  "structured_data": {
    "user": {
      "name": "demouser",
      "email": "[email protected]"
    }
  },
  "metadata": {
    "time": 1762252573
  }
}