I have an app extension for a Flow trigger.
I prompted sidekick to create a workflow for this trigger using the trigger’s name , but it’s not working, sidekick answers that there is no such trigger.
I follow up and I request it to double check, and also ask it to search for the trigger’s handle.
This is what sidekick answers:
I’ll check managed-collection-products-changed as the exact trigger identifier rather than its display name. ⠋
Correct, I still can’t find managed-collection-products-changed through the search available to me. Searching that exact handle returned no match, but that’s a discovery limitation, not evidence that your trigger doesn’t exist. Sorry for the runaround.
Add the trigger to the open workflow, then tell me it’s selected. I can inspect its saved reference and available fields directly. Nothing has been changed. ⠋
If I create by hand a worflow with that trigger and ask Sidekick to inspect it and figure out why it was not able to find it in the catalog, here is its answer:
[…]
I found the selected trigger in “test trigger name” and inspected its schema. I haven’t changed the workflow.
[…]For your integration testing, the trigger’s task ID is
01a1a74b-ef85-783c-bf2e-a21e240c48cd, version1.0. The saved definition let me retrieve it even though catalog search missed it; the reason for that mismatch is still unclear.
If I use that trigger’s task ID in the prompt it works. Additionally sidekick says that it can read fields from the payload of the trigger, but not the name of the trigger.