I’m building a custom trigger node using the declarative style (for Inoreader, but applies to any API trigger).
My node works perfectly in manual executions, but when I try to activate a workflow using it, I get:
400 There was a problem activating the workflow: "Could not get parameter"
What I’ve tried:
- Cleared all caches (
~/.n8n), npm links, rebuilt everything, created new workflows from scratch - Added/removed all optional parameters, used default/empty values, renamed the node
- Updated to the latest n8n and SDKs
What I noticed:
- Manual execution always works
- Activation always fails with this error, even with a brand new workflow and minimal config
- The only thing I see that’s “extra” is the global Settings tab (Batching, Proxy, Timeout, etc.) for the node, which isn’t defined in my node code, but is added by n8n UI to all HTTP/request-based nodes
Questions:
- Is there something required to make a custom trigger node “activatable” that’s not documented?
- Is there a specific property or technique to make activation work with these global Settings options?
- Is this a bug, or is there a current recommended workaround?
Happy to share code or workflow JSON if helpful.
Would appreciate any guidance—this is the last blocker to making my node public!
Thanks!