Create Automation Skill

Build automation workspace JSON, then create, update, or delete automations via qlik-mcp tools.

Scope

When the platform the automation needs to reach has no dedicated connector, or the resolved connector does not expose the needed block, do not stop — fall back to the generic connectors or the built-in CallUrlBlock as long as the platform has an HTTP API. See references/generic-connectors.md. Stop and tell the user the skill cannot help only when even that fallback cannot express the request (no HTTP API, or an auth flow the generic connectors do not support).

Three run modes are supported — manual, triggered and scheduled. Pick the one the request implies, then follow Run modes.

Workflow

1. Discover connectors and pick blocks via qlik-mcp tools

1. Resolve connectors via the MCP tool qlik_list_automation_connectors. It returns the live tenant connector list, each entry carrying id, name, description and other connector related information. Reference the returned id as datasourcetype_guid on connector blocks. ex: Filter syntax: filter='name eq "Qlik Cloud Services"'.
   • If the qlik-mcp is not connected, stop and ask the user to connect it. Do not guess or hardcode connector guids.
2. Fetch full connector detail with qlik_get_automation_connector(connector_id=<connector-guid>). It returns endpoints and snippets in two separate top-level arrays — the array an entry came from is what decides the block type:
   • blocks[] → build an EndpointBlock; the entry's id is its endpoint_guid.
   • snippets[] → build a SnippetBlock; the entry's id is its snippet_guid.