Pricing

Additional Parameters in Outgoing Integrations

Gain more control over how response data is saved in Synerise. You can now add custom parameters to outgoing integration events—perfect for tagging, filtering, or personalizing response logs without touching the external API.

We’ve just added more flexibility to Outgoing Integrations in Synerise. Whether you're using a custom webhook or setting up a reusable integration, you can now define additional parameters for the response event.

This small but powerful improvement helps you enrich the event that stores the response from your external system — with full control over the structure and content.

What’s new

When configuring an outgoing request (via Custom Webhook or in reusable integrations), you can now add key–value pairs to the response event. These will be included in the event when the response from the external system is stored.

These parameters:

  • Are fully customizable
  • Support dynamic values using Jinjava (e.g., based on data from the trigger or previous nodes)
  • Do not affect the original response, only the way it is saved in Synerise

Why it matters

Sometimes, storing the raw response is not enough. You may want to:

  • Add identifiers or metadata that make it easier to find and filter these events later
  • Differentiate requests that share the same structure but were sent in different contexts
  • Personalize saved responses based on the customer or trigger data

With support for Jinjava, values can reflect the exact context in which the request was made—making your automation smarter and your data cleaner.

How to get started

  1. Go to Integration > Outgoing
  2. Choose a custom webhook or reusable integration
  3. Define the request and the response event name
  4. In the new "Additional Event Parameters" section, add key–value pairs
  5. Use static values, or use Jinjava expressions to reference trigger data

Use Cases

We’ve expanded our use case catalog with new, real-world scenarios! 🚀 Built on insights from our customers and powered by the latest features in our platform, these use cases are designed to help you unlock even more value.
Automation

Additional Parameters in Outgoing Integrations

Gain more control over how response data is saved in Synerise. You can now add custom parameters to outgoing integration events—perfect for tagging, filtering, or personalizing response logs without touching the external API.

We’ve just added more flexibility to Outgoing Integrations in Synerise. Whether you're using a custom webhook or setting up a reusable integration, you can now define additional parameters for the response event.

This small but powerful improvement helps you enrich the event that stores the response from your external system — with full control over the structure and content.

What’s new

When configuring an outgoing request (via Custom Webhook or in reusable integrations), you can now add key–value pairs to the response event. These will be included in the event when the response from the external system is stored.

These parameters:

  • Are fully customizable
  • Support dynamic values using Jinjava (e.g., based on data from the trigger or previous nodes)
  • Do not affect the original response, only the way it is saved in Synerise

Why it matters

Sometimes, storing the raw response is not enough. You may want to:

  • Add identifiers or metadata that make it easier to find and filter these events later
  • Differentiate requests that share the same structure but were sent in different contexts
  • Personalize saved responses based on the customer or trigger data

With support for Jinjava, values can reflect the exact context in which the request was made—making your automation smarter and your data cleaner.

How to get started

  1. Go to Integration > Outgoing
  2. Choose a custom webhook or reusable integration
  3. Define the request and the response event name
  4. In the new "Additional Event Parameters" section, add key–value pairs
  5. Use static values, or use Jinjava expressions to reference trigger data
Product Newsletter
Stay up to date with the latest Synerise product updates, new features, and practical insights — delivered straight to your inbox. Just subscribe to our weekly communication!
Read about our privacy policy.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Key benefits

Explore the core advantages of this feature and discover the value it brings to your daily work with Synerise.

Better Event Structuring

Add identifying metadata to response events

Dynamic Personalization

Use Jinjava to adapt parameters based on customer or trigger context

Zero overhead

No changes needed in external APIs—this only affects how data is stored in Synerise

Use Cases

Explore real-life use cases that demonstrate how to apply this feature in practice through inspiring, ready-to-use scenarios that solve real challenges.
No items found.

Share your feedback with us!

Want to share your thoughts or have any questions about this article?
Leave us a message — we’d love to hear your opinion!
Synerise is the controller of your personal data processed for the purpose of fulfilling your request specified in this form. You may withdraw your consent at any time by contacting us. For more information on how we process your personal data and what rights you have, see our privacy policy.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.