Hi everyone,
We’ve identified an important limitation in Autom Mate triggers that impacts real-world enterprise integrations, especially with platforms like Salesforce.
The issue
Currently, when sending an XML payload to either a Webhook trigger or an API trigger, Autom Mate logs the request body as an empty object {}. XML content is not being recognized or parsed.
This creates a blocker for several enterprise use cases.
Why this matters
A common example is Salesforce classic upsert triggers, which send SOAP (XML-based) messages.
To properly support these scenarios, Autom Mate needs to:
-
Correctly accept and parse XML payloads in webhook/API triggers
-
Allow workflows to access XML fields (similar to how JSON is handled today)
-
Ideally, support customizable response bodies, since Salesforce SOAP requests require a valid acknowledgment response
Right now, Autom Mate does not allow response customization for these triggers, which makes full SOAP compatibility impossible.
Suggested enhancement for upcoming release
-
Native XML payload support in Webhook and API triggers
-
Automatic XML → structured object parsing
-
Ability to define custom HTTP/SOAP responses in trigger configuration
This would significantly improve Autom Mate’s readiness for enterprise integrations and legacy platform interoperability.