Resources · Zapier integration

Let's Get Digital Zapier integrationAutomate Let's Get Digital with Zapier.

Let's Get Digital Zapier integration: 4 triggers, 3 actions, 1 search. Zapier can react the moment a user is created, updated, deleted or checked in on Let's Get Digital, and manage users from other apps. Works on the free plan. Below: costs, connection, a first Zap, what breaks.

See the 8 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Let's Get Digital Zapier integration does for you

The Let's Get Digital Zapier integration connects your Let's Get Digital account to Zapier so its users stay in step with the rest of your tools. Let's Get Digital is a platform for event organisers who want their events to hit their targets. Zapier passes every change on its users to other apps, and can create, change or remove users from outside.

Three results come up again and again. A heads-up on every check-in: User Check-In or Check-Out fires as soon as someone is checked in or out, and a message lands in your team chat so everyone sees who came and went without asking around. A contact for every new user: User Created reports each new user, and a contact appears in your CRM without anyone exporting a list. Records that match across tools: when a row changes in your spreadsheet, Get User finds the matching user and Update User writes the change into Let's Get Digital (one source of truth, two places kept in line).

What Zapier does not do here matters just as much. Update User and Delete User both need the user's ID, so a Zap that starts elsewhere has to find that ID first, usually with Get User. There is no find-or-create pairing either: if the search comes back empty, Zapier will not create the user for you in the same step. And all four triggers only see what happens after the Zap is on. If you are weighing other tools for this, see n8n vs Zapier and our Zapier review.

Vocabulary

Zapier vocabulary in one minute

Eight words come back all over this page. Here is what each one means in plain terms.

Zap
The automation you build in Zapier: one trigger first, then one or more actions that run every time that trigger event happens.
Trigger
The event that starts a Zap, such as a user checking in. Once the Zap is on, Zapier waits for it.
Action
What the Zap does after it starts: the step that writes, sends or moves something for you, such as updating a user.
Task
The unit Zapier bills. One action that completes successfully counts as one task, and your plan allowance is a count of those.
Polling vs instant
A polling trigger is checked on a timer. An instant trigger is reported by the app the moment it happens. All four here are instant.
Filter
A step that lets the Zap carry on only when what arrived meets a condition you set, and stops it right there otherwise.
Search step
A step that looks up something that already exists in an app, such as a user, so the steps after it can use what it found.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action, a filter or a search turns a Zap into one, and it then needs a paid plan.
Cost

What a Let's Get Digital Zap really costs

The four triggers never cost a task. Since they are instant, Let's Get Digital tells Zapier itself, and nothing waits for a scheduled check.

  • Trigger cost0 tasks
  • Free plan100 tasks a month
  • Free plan Zap size2 steps
  • Premium appNo

What gets billed is each action that succeeds: a user created, updated or deleted, a message sent. An action that fails is not counted. A Zap with two actions spends twice as much per check-in as one with a single action. The free plan gives you 100 tasks a month and Zaps of two steps: a trigger plus one action. Add a filter, a second action or the Get User search and the Zap is multi-step, so it needs a paid plan. Let's Get Digital is not a premium app, so it works on the free plan. The interval grid below concerns polling triggers only.

Connect

Connect Let's Get Digital to Zapier in three steps

  1. 01

    Open the Apps page

    Sign in to Zapier and go to the Apps page of your account. Before you start, check that you have a Let's Get Digital account of your own, plus access to any user record you do not own but want a Zap to change.

  2. 02

    Add Let's Get Digital

    Click + Add connection, type Let's Get Digital in the search box of the dialog and pick it from the list. Then click Add connection: a new browser tab opens on the Let's Get Digital side.

  3. 03

    Sign in and grant access

    In that tab, sign in to Let's Get Digital and grant Zapier access to the account. The connection now sits on your Apps page, and every Zap step that uses Let's Get Digital reuses it without asking again.

First Zap

Your first Zap: log qualifying check-ins in a spreadsheet

GoalEach check-in or check-out that passes your condition becomes a new row in your spreadsheet.

  1. 01

    Create the Zap and pick the trigger

    In Zapier, start a new Zap, choose Let's Get Digital as the app that starts it and User Check-In or Check-Out as the event. Select the connection you added earlier.

  2. 02

    Test the trigger

    Check a test user in, then run the trigger test. Zapier brings back the three most recent items of the account, so you map the next steps on a real check-in.

  3. 03

    Add the filter

    Add a Filter step from the plus icon and fill its three boxes: the field to look at, the rule and the value. Pick a rule that matches the field type, or nothing gets through.

  4. 04

    Add the spreadsheet action

    Add the action in your spreadsheet app and map what the trigger brought back into the columns. With a filter, this Zap is multi-step and needs a paid plan.

  5. 05

    Test, then publish

    Run each step once and check the row. Then click Publish. Since the trigger is instant, each check-in that passes the filter is logged as soon as Let's Get Digital reports it.

Triggers

The four Let's Get Digital triggers

4 events start a Zap when something happens in Let's Get Digital, and 4 of them are instant: the app calls Zapier straight away, whatever your plan.

1

User Check-In or Check-Out

Instant trigger

In Zapier“Triggers when a user is checked in or out.”

Starts the Zap whenever a user is checked in or checked out: the only one of the four that follows comings and goings rather than the user record.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
you want your team, or a sheet, to know who has checked in or out without anyone having to ask.
Watch out
one trigger covers both directions, so add a filter if only check-ins, or only check-outs, should go on.
2

User Created

Instant trigger

In Zapier“Triggers when a new user is created.”

Reports each new user the moment the record exists in Let's Get Digital, so other tools hear about newcomers straight away.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
every new user should also become a contact in your CRM or a subscriber in your mailing tool.
Watch out
a Zap that uses Create User elsewhere will set this trigger off too, so check that two Zaps are not feeding each other.
3

User Deleted

Instant trigger

In Zapier“Triggers when a user gets deleted.”

Fires when a user gets removed from Let's Get Digital, which is the signal for cleaning up the same person in the other apps you use.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a removed user should also be flagged or removed in your CRM or your sheet, so lists stay consistent.
Watch out
users deleted before the Zap was published are never sent, so an older clean-up has to be done by hand.
4

User Updated

Instant trigger

In Zapier“Triggers when a user get updated.”

Picks up any change saved on an existing user and hands the updated record to the steps that follow.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
details edited in Let's Get Digital should flow into the other tools that hold the same person.
Watch out
never pair it with Update User on the same user in one Zap; each update sets the trigger off again and the Zap loops through your tasks.
Actions

The Let's Get Digital actions

Let's Get Digital gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create User

Action

In Zapier“Creates a user in the system”

Adds a new user to Let's Get Digital from data that arrived in an earlier step, so people signing up elsewhere end up on the platform too.

When to use it
sign-ups happen in a form or another tool and should not be retyped.
Watch out
there is no find-or-create here, so run Get User first if duplicates matter.
2

Delete User

Action

In Zapier“Deletes a user in the system”

Removes a user from Let's Get Digital, the counterpart of a deletion or an unsubscribe in another app.

When to use it
someone leaves a list elsewhere and should leave the platform as well.
Watch out
the user ID is required, so test it on a user you created just for the test before switching the Zap on.
3

Update User

Action

In Zapier“Updates a user in the system”

Writes changes onto an existing user in Let's Get Digital, keeping their record in line with another source.

When to use it
details change in your CRM or a sheet and the platform should follow.
Watch out
the user ID is required, so a Get User step usually comes first; and avoid pairing it with the User Updated trigger.
Searches

The Let's Get Digital search

1 search step looks for data that already exists in Let's Get Digital, so a later step can use it.

A search step looks up a user who already exists and passes what it found to the next steps. In the editor, Get User sits at the bottom of the action-event list, under its own SEARCH heading. A search makes the Zap multi-step, so it needs a paid plan.

1

Get User

Search

In Zapier“Finds a user in the platform”

Finds a user on the platform and hands their record, ID included, to the next steps, which is how a Zap started elsewhere gets the ID that Update User and Delete User require.

When to use it
a change starts in another app and has to land on the right person in Let's Get Digital.
Watch out
whether it wants an exact value or something close is up to Let's Get Digital, so test it with a real user.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nobody stops the Zap there and the steps that depend on it are skipped. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. Let's Get Digital exposes no find-or-create pairing, so do not count on Get User creating a missing user.
  3. If multiple search results are found?
    Three ways out when several users match: keep the first one, which is the default, stop the Zap, or hand all of them on at once.
When it breaks

When a Let's Get Digital Zap breaks

Zapier attaches no help article to Let's Get Digital, and no rate limit is documented for it. The risks are the general ones every Zap runs into, and this app makes one of them very easy to hit.

None of them shows up as a big red error at first. They show up as users missing from a list, a task count that drops faster than planned, or a Zap that looks on but does nothing. When one of them hits, start with Zapier troubleshooting.

  • Earlier changes never come through

    A Zap only reacts to what happens after it is switched on. Users created, updated or checked in before you published stay as they are; that backlog is a separate job.

  • User Updated and Update User in a loop

    A Zap that writes into the very place its own trigger watches sets itself off again and again. Updating a user from a Zap that listens to user updates is the textbook case.

  • A bulk import gets held back

    When a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold it back instead of running every user through.

  • A search that finds nobody

    With the default setting, a Get User search that comes back empty stops the Zap there, and the Update User or Delete User step after it is skipped.
Need help

Need help automating Let's Get Digital with Zapier?

A person reads every message.

FAQ

Let's Get Digital and Zapier: common questions

01Is the Let's Get Digital Zapier integration free?
Yes, on Zapier's free plan. Let's Get Digital is not a premium app, so you can connect it without paying for Zapier. The free plan gives you 100 tasks a month and Zaps of two steps: one of the four triggers, such as User Check-In or Check-Out, plus one action, for example a message in your team chat. As soon as you add a filter, a second action, or a Get User search before Update User, the Zap becomes multi-step and needs a paid plan. Triggers never cost a task, so only actions that succeed count.
02How many tasks does a Let's Get Digital Zap use?
One task per successful action, per event. Triggers are free. If 40 people check in and each check-in posts one chat message, that is 40 tasks. Log each check-in in a sheet as well and the same 40 cost twice as much. An action that fails is not counted against your plan. A few apps take more than one task per action, so if your count drops faster than expected, look at every action in the Zap.
03Are Let's Get Digital triggers real time?
Yes. All four triggers, User Check-In or Check-Out, User Created, User Deleted and User Updated, are instant: Let's Get Digital tells Zapier the moment the event happens, so the Zap starts right away whatever your plan. The polling grid of the plans, 15 minutes on Free down to 1 minute on Team and Enterprise, does not apply to them. In the editor, a Zap built on an instant trigger shows a lightning bolt. That is good news on a free plan: a check-in reaches the next app without waiting for any scheduled check.
04What does connecting Let's Get Digital to Zapier require?
A Let's Get Digital account, a Zapier account, and access to any user record you do not own but want a Zap to change. The steps: open the Apps page in Zapier, click + Add connection, search for Let's Get Digital and pick it, then click Add connection. A tab opens where you sign in to Let's Get Digital and grant Zapier access. The connection then sits on the Apps page and every Zap reuses it. For Update User and Delete User, also plan where the user ID will come from, since both require it.
05Why does Update User keep firing over and over?
Because the Zap is probably listening to User Updated and writing with Update User on the same user. Each update the action makes is a new update for the trigger, so the Zap starts again, updates again, and burns through your tasks. Break the circle: either start from another app and use Get User then Update User, or use User Updated only to send changes out to other tools, never back in. If you need both directions, keep them in two Zaps and add a filter so a change that came from Zapier does not go round again.
06What if the Let's Get Digital operation you need is not on Zapier?
Then it is not available through Zapier for this app right now. The editor lists eight Let's Get Digital operations: four user triggers, the Create User, Update User and Delete User actions, and the Get User search. Everything revolves around users; nothing else on the platform is exposed to Zapier, and there is no find-or-create pairing. For other parts of the job, the options are to handle them inside Let's Get Digital or to look at what other automation tools offer for the same app. Write down the exact result you are after first.
07Zapier, Make or n8n for Let's Get Digital?
Decide on criteria, not on a ranking. Coverage: on Zapier, Let's Get Digital offers four instant triggers, three actions and one search, all about users, so check what each tool lists for the app before choosing. Speed: the triggers are instant here, so the plan does not slow them down. Cost: on Zapier every successful action is a task, so estimate your monthly check-ins and user changes and multiply by the number of actions. Complexity: a search or a filter makes the Zap multi-step and needs a paid plan. Run the same checks on each tool.
Same platform

Other docs you might need on this stack.

Browse all integrations