Add new Qlik users to an Airtable directory automatically

Each time a user is created in Qlik, FlowMattic adds a record for them to your Airtable base, building a directory of Qlik accounts you can sort, tag and share.

Qlik

Airtable

Download this workflow Browse more workflows

2 steps Setup ~5 min Used on 653 sites Free to import

The Add new Qlik users to an Airtable directory automatically workflow on the FlowMattic canvas, with 2 steps across Qlik, Airtable — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

Qlik admins often need a list of who has an account outside Qlik itself: for licence reviews, onboarding checklists or a quick look-up by the support team. This workflow keeps that list in Airtable, adding one record whenever a new Qlik user appears.

The Qlik Users trigger can fire when a user is created or deleted. Which of the two it sends depends on the webhook you set up in Qlik, so subscribe that webhook only to the user Created event. If you also tick Deleted, removed users would arrive as new records in the directory too.

Next, Airtable Create Record writes the new Qlik user into the base and table you pick. It ships unmapped, so after import you connect Airtable, pick the table and map the Qlik user fields you want into its columns, for example the name, email and the date the account was created. Run a test by adding a user in Qlik and look at the payload in FlowMattic to see which fields Qlik sends.

Each created user gives one new record. The workflow doesn't look for an existing record first, so a user who is deleted and added again later gets a second row.

Licence review list for Qlik admins

An analytics lead opens the Airtable directory at the end of each quarter to see every Qlik account created since the last review, and marks which ones still need a licence.

Onboarding tracker for new analysts

Each new Qlik user lands in an Airtable table with extra columns for training status, so the team lead can tick off the dashboard walkthrough and data access request.

Shared directory for the help desk

Support staff without Qlik admin rights search the Airtable base to confirm whether a colleague already has a Qlik account before raising an access ticket.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
Qlik Users
Fires when Qlik reports a user event. FlowMattic describes this trigger as covering users that are created or deleted, so set the Qlik webhook to send only the Created event for this directory.
Step 2Action
Airtable Create Record
Adds a new record to the Airtable table you choose. The Qlik fields aren't mapped yet, so connect your base, pick the table, then map the Qlik user details into the fields you want to keep.

What you need

FlowMatticCore
Qlik AccountAccount
Airtable AccountAccount

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

Add a Created On column in Airtable and, if the Qlik payload carries a timestamp, map it there so you can filter the directory by month.
If you want a record of deletions too, build a second workflow with its own Qlik webhook subscribed only to Deleted, and have it add records to a separate Removed Users table.
Keep a Notes or Owner column in the Airtable table that the workflow doesn't touch, so your team can add context by hand without it being overwritten.

Questions about this workflow

Will deleted Qlik users show up in my Airtable directory?

Only if the Qlik webhook sends deletion events. The Users trigger can carry both Created and Deleted, so choose just Created when you set up the webhook in Qlik.

Are existing Qlik users added when I turn the workflow on?

No. Only users created after the webhook is in place start a run. Add your current users to the Airtable table once, by hand or with a CSV import, to fill it.

Which Qlik user fields can I store in Airtable?

Whatever the Qlik webhook payload contains. Create a test user, look at the data FlowMattic received, and map those values into your Airtable columns in the Create Record step.

What happens if the same person gets a new Qlik account later?

The Create Record step always adds a new row, so that person appears twice in Airtable. For one row per person, put Airtable's Search Record action between the Qlik trigger and Create Record to look the email up first. Then put a Filter between Search Record and Create Record that continues only when no match came back; a test run shows what the search returns for a new email.