Week 42: Truto's Weekly Changelog + Weekend Bug Bash

Don't break your head over integrations

Integrations are a solved problem with Truto. Why have your best engineers work on integrations instead of critical features, security, architecture, and infrastructure updates for your product?

Speak with us to learn more about how we are helping companies like Sprinto delegate their integrations to Truto.

New

New integrations

• Elastic Cloud?— supports the Unified User Directory API.

• LinkedIn?— supports the Unified Ads Management API.

• Brevo?— supports the Unified Marketing Automation API.

• FreeAgent?— supports the Unified Accounting API.

Improvement

• We’ve added support for the?unified/ads/custom_audiences?resource for Meta Marketing API.

• Expanded support with?create?and?update?endpoints, including custom fields, for seamless integration with?Affinity?through our Unified CRM API.

• Now, you can create and update custom fields across resources for?Insightly,?Pipedrive, and?Outreach?integrations in the Unified CRM API. More flexibility for your CRM workflows!

Weekend Bug Bash

When we set out to squash bugs over the weekend, little did we know we would also end up going down the feature squash rabbit hole. It was an eventful weekend. Here's what came out of it:

Introducing the Truto Catalog

Explore all available integrations and unified APIs in a single, consolidated view. Stay tuned—more features are coming soon!

Impersonation Controls

You’re in charge! Choose to allow or restrict Truto's support team from impersonating your team members. All actions are fully logged and auditable.

Logo Uploads Made Easy

You can now upload your team’s logo and update any integration’s logo or icon directly within the Truto console — no need to host the file yourself.

Stability Improvements?

We've made improvements to our logging infrastructure to ensure better reliability.

Error Mapping Enhancements

We've improved support for mapping the?metadata?object in?error_mapping?to give you more control over configuring errors when the underlying API lacks proper error handling.

For example, in the?Unified API, the error mapping might look like this:

error_mapping: | 
    error.{ 
        "message": message, 
        "metadata": { 
        "id": request_id, 
        "details": details 
    } 
}        

and for a specific integration's error mapping, it could look like:

That's it from us for the past week. We would love your feedback on all the new updates and features!

Refer Truto to another team

Know someone who can benefit from Truto? Introduce them to us at [email protected]

Truto offers a 20% referral bonus for each successful referral.