Changelog
Custom Tool Embeds
We've completely overhauled our tool embedding system, making it more intuitive, customizable, and user-friendly.
When integrating AI tools, you often need seamless design customization and real-time previews. This update brings:
✅ Live Preview – See how your tool embed will look before implementation
✅ Style Customization – Set your primary color scheme and adjust the CTA text
✅ User Guidance – Add helpful tips to guide users through the tool
✅ Enhanced UI – A refreshed, cleaner interface for a better user experience
To get started, configure your Custom Tool Embed settings within Relevance AI.
This update makes embedding AI tools easier, more flexible, and better tailored to your brand and user experience.
If you're interested in trying out Relevance AI and Custom Tool Embeds, you can sign up to get started or book a demo to see it in action.
Other improvements
Webhook Trigger Improvements 🔗
We're excited to announce a major upgrade to our webhook trigger system!
We've made it easier to trigger actions with webhooks by offering more flexible configuration. This means you can now integrate third-party systems and automate tasks without needing native support.
When setting up your custom webhook, you’ll be given a unique URL to send requests that will trigger actions.
You also have full control over your payload format. Customize inputs easily using the message template with double brackets, or include your entire document with {{$}}. For example, you can personalize your message like this: “Hello {{first_name}}, thanks for your order!”
Additionally, on the custom webhook edit page, you can map a Thread ID or a Unique ID to your payload:
A Thread ID is used when you want to continuously send new information to the same agent conversation, such as in a chatbot use case. Simply map the request body key to be used as the Thread ID.
A Unique ID prevents processing the same event multiple times. If an event with the same Unique ID is received again, it will be ignored, ensuring that duplicate events are not processed.
