Skip to main content
Question

Bug: credentialsValues is empty {} when triggering from an Automation Template (Works fine when you create automation from scratch)

  • April 16, 2026
  • 1 reply
  • 41 views

Hi everyone,

I'm running into an issue with the Apps Framework regarding custom automations, and I wanted to see if anyone else has experienced this or if it's a known bug.

The Setup:
I've built an integration that relies on a custom trigger for file uploads. In the setup, the user authorizes and selects their credentials, which are tied to their external platform's team ID and user ID.

The Issue:
When a user builds the automation from scratch using the custom recipe, everything works perfectly. The credentialsValues object is properly populated in the webhook payload, allowing us to route the request to the correct external team.

However, when we package this exact same setup into an Automation Template and the user installs it, the webhook fires but the credentialsValues object drops entirely and comes through as empty ({}).

I think this wouldn’t be the expected behaviour. 

1 reply

Facing the same issue for a month.

I raised a support ticket on March 17.

Hope it gets fixed soon.