Goal β understand why headers arenβt replayed
Explain why Trigger Header shows {} when running an Autom manually after a webhook trigger, even though the Trigger Param (body) is preserved.
When to Use β scenarios & prerequisites
-
Autom trigger type = Webhook
-
Webhook call includes both Trigger Body and Trigger Header
-
User later clicks Run manually in the interface
-
Observed: last body is replayed, but headers are missing
Step-by-Step β what happens internally
-
Initial Webhook Trigger
-
Autom receives both Trigger Body (params) and Trigger Header
-
Body and headers are visible in the run log
-
-
Manual Run After Webhook
-
Autom Mate reuses the last Trigger Body for convenience
-
However, Trigger Header is not stored, so it comes through as
{}
-
-
Result in Logs
-
Trigger Param β populated with last request body
-
Trigger Header β empty object
{}
-
Architecture / Flow β simplified view
-
Webhook trigger (headers included):
External Client β Webhook β Autom (Body β , Header β ) -
Manual run (body replay, headers empty):
Manual Run β Autom (Body β , Header β)
As of Autom Mate v4.7.0, headers are not persisted. Only the last body (params) is stored and reused for manual runs.
Validation β how to confirm
-
Trigger Autom via webhook with headers β open run log β both Trigger Body and Trigger Header visible
-
Click Run manually afterwards β Trigger Body is reused, Trigger Header shows
{}
Troubleshooting β common pitfalls
-
Auth headers missing: If your Autom depends on headers like
Authorization, it will fail in manual runs. -
Environment headers not replayed: Values such as
x-envwonβt be visible unless resent via webhook.
Best Practices
-
Use Webhook calls to fully test scenarios with headers.
-
If headers must persist, raise a Feature Request so product can plan it for future versions.
At a glance:
-
Components: Webhook Trigger, Manual Run, Logs
-
Autom Mate Version: 4.7.0 (behavior confirmed)
-
Limitation: Headers not persisted; Body is reused