Triggers
ancoreMate triggers start your flow or workflow the moment something happens in Qlik Cloud – a reload finishes, an app is published, an automation run fails, an ancoreShare report is ready. There is no polling and no delay of minutes.
Available triggers
| Connector | Triggers |
|---|---|
| ancoreMate Apps | When an app is created, published or exported, when the data of an app is updated |
| ancoreMate Reloads | When an app reload finishes – also for reloads started by reload tasks |
| ancoreMate Automations | When an automation is created, updated or deleted, when an automation run starts, ends or fails |
| ancoreMate ancoreShare Reports | When an ancoreShare report is finished – see ancoreShare reports |
In n8n, all triggers are events of the node ancoreMate Trigger: add it and choose the Event.
How a trigger works
- Turn on. When you save and turn on a flow in Power Automate, or activate a workflow in n8n, the tool registers the trigger with ancoreMate. ancoreMate creates a webhook in Qlik Cloud for the connected Qlik Cloud user.
- Event. Qlik Cloud reports the event to ancoreMate, and ancoreMate passes it on to your flow at once. If the flow cannot be reached, ancoreMate tries again several times.
- Turn off. When you turn the flow off or delete it, or deactivate the workflow, the tool unregisters the trigger and ancoreMate deletes the webhook in Qlik Cloud. If a flow no longer exists, ancoreMate turns its trigger off by itself.
Filters
Most triggers have optional filters – for example App, Space or Result (only successful or only failed reloads). Leave a filter empty to get all events. Filters keep your flow quiet: it only runs for the events you care about.
Triggers and Qlik Cloud connections
A trigger keeps the Qlik Cloud connection it was turned on with. If you change the Qlik Cloud connection of a connection in Power Automate or n8n, turn the flow or workflow off and on again so that the trigger uses the new one. When you remove a Qlik Cloud connection, its triggers end at once; after you have signed in the connections again, turn their flows and workflows off and on. See Connect ancoreMate to Qlik Cloud.
Whose events
A trigger receives the events that the connected Qlik Cloud user may see, like the webhooks a user creates in Qlik Cloud. Events that Qlik Cloud only offers to the whole tenant – for example "app deleted", "user created" or "API key rejected" – are not available to ancoreMate, also not for tenant administrators.
Tips
- React to a reload task: Qlik Cloud does not report which reload task started a reload. Use When an app reload finishes with the app of the task.
- Failed reloads only: set Result to
errorand send the error message to the app owner. - n8n: your n8n webhook address must be reachable from the internet over HTTPS, otherwise ancoreMate cannot deliver the events.
- Test: turn the flow on, trigger the event in Qlik Cloud (for example reload the app by hand) and watch the run history.