Resources · Zapier integration

inwink Zapier integrationAutomate inwink with Zapier.

inwink Zapier integration: 14 triggers, 6 actions and 3 searches. 13 of those triggers are instant, the app runs on the free plan, and this page walks you through every operation, what it costs you and what breaks, before you even open Zapier.

See the 23 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the inwink Zapier integration does for your events

The inwink Zapier integration links your event platform to the rest of your tools, with no code. Zapier spots what happens in inwink (a registration, a check-in, a survey answer, an order) and then creates, updates or looks up records for you, in inwink or elsewhere. You link your inwink account once and every automation reuses it.

A community that fills itself with real attendees. Person Attended starts the automation when the Has Attended box gets ticked, and Create Member adds that person to a community. People who registered and never came stay out.

A sales team that hears about every order. Order Added and Order Updated hand each order to the tool your sales or finance people read, the moment inwink records it.

Session lists that match reality. Person Registered to Session and Person Attended to Session follow your agenda talk by talk, so a speaker's follow-up goes to the people who actually sat in the room.

What Zapier does not do with inwink: no action deletes anything, so a person, member or company removed elsewhere stays in inwink until someone clears it by hand. Nothing picks up past registrations either. And every update action needs the inwink ID of the record, which an earlier step has to supply.

If you are weighing platforms, the inwink Make integration page covers the same app on Make, and our n8n vs Zapier comparison lays out the criteria between those two.

Vocabulary

Zapier vocabulary in one minute

Eight words come back on every line of this page. Here is what each one means, in plain terms.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time that trigger event happens.
Trigger
The inwink event that starts a Zap, such as a new registration or a survey answer. Once the Zap is on, Zapier waits for it.
Action
What the Zap does after it starts: the step that creates or updates something for you, in inwink or in another tool.
Task
The unit Zapier bills. One task is one action that completed successfully; the count on your plan counts those and nothing else.
Polling vs instant
Polling: Zapier asks the app for new items on a timer. Instant: the app calls Zapier the moment it happens. 13 of 14 inwink triggers are instant.
Filter
A step that lets the Zap go on only when the incoming data meets the condition you set, and stops it there otherwise.
Search step
A step that looks up a record that already exists, a person by email for example, so the steps after it can use what it found.
Connection
Your inwink account, linked to Zapier one time, then reused by every step of every Zap that reads from or writes to inwink.
Cost

What it really costs

inwink is not a premium app, so it works from the free plan. The trigger never costs a task, however often Zapier checks: only an action that completes is billed.

  • Free plan100 tasks a month
  • Steps allowed on the free plan2 (one trigger, one action)
  • Premium appNo
  • Instant triggers13 of 14

Each successful action counts on its own, so a three-action Zap eats three times what a one-action Zap does, and a failed action costs nothing. The free plan gives 100 tasks a month but stops at two steps: one trigger, one action. Add a filter, a search or a second action and you get a multi-step Zap, which needs a paid plan. The interval grid below only concerns Search by Email; the 13 other triggers start right away on any plan.

Connect

Connect inwink to Zapier in three steps

  1. 01

    Open your connections

    In Zapier, go to the Apps page of your account and click + Add connection. A dialog opens with a search box: type inwink and pick it from the results.

  2. 02

    Sign in to inwink

    Click Add connection. A new tab opens on inwink: sign in with the account your Zaps should act as. It needs access to every event and community you do not own yourself but want a Zap to touch.

  3. 03

    Grant access

    Approve the access Zapier asks for in that tab. The connection then appears on your Apps page, and every inwink step reuses it: you sign in once, not once per Zap.

First Zap

Your first Zap: registrants into a community

GoalEach new registrant of an event becomes a member of your community, as long as an email address came through.

  1. 01

    Build the trigger

    Create a new Zap, pick inwink as the app that starts it and Person Registered as the event, then select the connection you made above.

  2. 02

    Choose your event and test

    Choose your event in the one required box, then test the trigger. Zapier brings back the three most recent registrants of that event, so you map fields from a real person.

  3. 03

    Add the filter

    From the plus icon, add a Filter step: Email as the field to look at, and a text rule that checks it is filled. This step makes the Zap multi-step, so it needs a paid plan; on the free plan, skip it.

  4. 04

    Add Create Member

    Add the action: inwink, then Create Member. Pick the CommunityId of the community to fill and map the registrant's email into the Email box. Both are required.

  5. 05

    Test the action

    Run the action once and open the community in inwink: the new member should be there. If it is not, read what Zapier sent back before you go any further.

  6. 06

    Publish

    Publish the Zap to switch it on. From then on, each new registrant costs one task when the member gets created. People who registered before you published stay out.

Triggers

inwink triggers: 14 events that can start a Zap

14 events start a Zap when something happens in inwink, and 13 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Person Added

Instant trigger

In Zapier“Triggers when a person is added in inwink person list”

A person lands in the person list of one of your events, and the Zap starts with that record in hand, ready for 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
your CRM or mailing tool should keep a copy of everyone added to an event list, whether by hand or by another tool.
Watch out
you choose your event before anything else, and the Zap only follows the event picked in that box.
2

Community Company Added

Instant trigger

In Zapier“Triggers when a company is added in inwink company list”

Whatever a company is to you (sponsor, exhibitor, client), this trigger passes it on as soon as it joins the company list of a community.

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 a matching account in your CRM the day a partner company shows up in inwink, without retyping its name.
Watch out
it asks you to choose your community, so a company added to another community will not start this Zap.
3

Community Company Updated

Instant trigger

In Zapier“Triggers when a company is updated in inwink company list”

Changes to a company that already exists are what this one listens for: a new name, a corrected detail, any edit saved in the company list of a community.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
after Community Company Added has opened the account in your CRM, this one keeps it in line.
Watch out
a Zap that also runs Update Community Company on that same community edits the company, which sets this trigger off again.
4

Community Member Added

Instant trigger

In Zapier“Triggers when a person is added in inwink member list”

New faces in a community's member list start this Zap, one run for each member added to the community you pick.

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 welcome sequence in your email tool should go out to each person who joins the community, with no one copying addresses.
Watch out
members created by Create Member in another Zap join the same list, so they start this one too. Plan for that chain.
5

Order Added

Instant trigger

In Zapier“Triggers when a new order is created in inwink”

Orders are where the money side of an event shows up, and this trigger fires each time inwink records a new one for the event you choose.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
finance wants a line in its spreadsheet, or a message in a team channel, for every order placed.
Watch out
an order edited after it was created does not fire this trigger again; that is the job of Order Updated.
6

Person Attended to Session

Instant trigger

In Zapier“Triggers when a person attended to a session”

Attendance gets tracked talk by talk here: the Zap starts when a person is marked as having attended a given session of your event.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
the slides of a workshop should reach the people who were in that room, and only them.
Watch out
the Zap runs once per person and per session, so on a packed agenda each action behind it adds up in tasks quickly.
7

Person Attended

Instant trigger

In Zapier“Triggers when a person attend the event (Has Attended is checked)”

The Has Attended box is the signal: once it gets ticked on a person, inwink tells Zapier that this person came to the event.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
attendees should get a thank-you, while no-shows get a replay link from another Zap.
Watch out
people checked in before the Zap was published are not picked up; only boxes ticked afterwards start it.
8

Person Registered

Instant trigger

In Zapier“Triggers when a new person registered the event”

Registrations are the classic starting point: someone new signs up for the event, and the Zap receives that person's 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
each registrant should land in your CRM as a lead, or your sales team should hear about sign-ups from target accounts.
Watch out
keeping only some registrants means adding a filter, and a filter already pushes the Zap onto a paid plan.
9

Person Registered to Session

Instant trigger

In Zapier“Triggers when a person registered to a session”

Some events ask for a second, finer sign-up, and this trigger catches the moment a person registers to one specific session.

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 speaker wants the list of people expected in their session, updated as sign-ups come in.
Watch out
signing up to a session and showing up are two different triggers; use Person Attended to Session to know who actually came.
10

Search by Email

Polling trigger

In Zapier“Search if a person exist, using the email adresse”

Unlike the 13 others, this one does not wait for inwink to call: Zapier checks your event for a person matching the email address you type in.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
you are waiting for one precise person, a speaker or a key guest, to appear in an event.
Watch out
it is the only polling trigger of the app, and both Email and the event are required before it can run.
11

Survey Answered

Instant trigger

In Zapier“Triggers when an answer is added to a survey”

Feedback forms feed this one: every answer added to a survey starts the Zap, with the responses ready to map into the next step.

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 collect satisfaction answers in a spreadsheet the product team reads after the event.
Watch out
you must choose your event and then your survey, so one Zap follows one survey; a second survey means a second Zap.
12

Community Member Updated

Instant trigger

In Zapier“Triggers when a member is updated”

Edits to a member record in the community you choose are what this trigger reports, whatever field changed.

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 newsletter list or a member directory outside inwink should follow the details people change in their profile.
Watch out
running Update Member on that same community from this Zap edits the member again and restarts the Zap, a loop that drains tasks.
13

Order Updated

Instant trigger

In Zapier“Triggers when an order is updated”

Once an order exists, any later change to it fires this trigger, so the tools downstream keep matching what inwink holds.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
the line that Order Added wrote in your finance sheet should change when the order changes.
Watch out
on its own, this trigger never sees the first version of an order; pair it with Order Added in a separate Zap.
14

Person Updated

Instant trigger

In Zapier“Triggers when a person is updated”

Whenever a person's record changes in the event you choose, Zapier hears about it and the Zap gets the updated 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
a phone number or a job title corrected in inwink should reach your CRM the same day.
Watch out
never point Update Person at the event this trigger watches: the Zap would rewrite the person and start itself over and over.
Actions

inwink actions: what a Zap can write in inwink

inwink gives you 6 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Community Company

Action

In Zapier“Create a new company”

Adds a company to one of your communities under the name you map, so an organisation captured elsewhere gets its own record in inwink.

When to use it
a deal marked won in your CRM should open the partner's company page in your community.
Watch out
CommunityId and Name are both required, so map each from a field that is never empty.
2

Create Member

Action

In Zapier“Create a new Member”

Turns an email address into a member of the community you point it to, with no manual invite.

When to use it
attendees, customers or newsletter readers should join your community the moment another tool knows about them.
Watch out
CommunityId and Email are required, and each member created here also starts any Zap built on Community Member Added.
3

Register Person

Action

In Zapier“Register a new person to an event manager with inwink”

Registers someone to one of your events, as a sign-up form would, but from any tool Zapier can reach.

When to use it
a lead captured on a landing page or in a webinar tool should end up registered to your next event.
Watch out
Event ID, First Name and Last Name are required, and the Event ID is read in your inwink back-office URL, not picked from a list.
4

Update Community Company

Action

In Zapier“Update en existing community company”

Edits a company that already sits in a community, found through its Company Id.

When to use it
your CRM changes a partner's details and the company page in inwink should follow.
Watch out
no search on this app looks companies up, so the Company Id has to come from an earlier step, such as one of the two company triggers.
5

Update Member

Action

In Zapier“Update an existing member”

Rewrites the record of an existing member, picked by Member Id inside the community you choose.

When to use it
a status or a detail updated in your membership tool should be mirrored in inwink.
Watch out
no search returns a member, so the Member Id must come from a previous step, Community Member Added for instance.
6

Update Person

Action

In Zapier“Update a Person”

Changes a person's record in the event you choose, using that person's Person ID.

When to use it
information your sales team adds in the CRM should flow back to the attendee in inwink.
Watch out
Person ID is required; Search Single Email can find the person from an email first. Keep it away from the event a Person Updated Zap watches.
Searches

inwink searches: find a person or a membership level

3 search steps look for data that already exists in inwink, so a later step can use it.

A search step looks something up in inwink and hands it to the steps after it. On inwink, that is how an email address turns into the person record an update needs. Searches sit at the bottom of the action event list, under SEARCH, and any search makes the Zap multi-step, so it needs a paid plan.

1

Search Membership Level by Id

Search

In Zapier“Search a membership level with a specific id”

Fetches a membership level of a community from its id, so later steps can read the level itself rather than a bare code.

When to use it
a step gives you a level id and the welcome email should name the level the member belongs to.
Watch out
you choose your community first, and the search only looks inside that one.
2

Search Person Field With Single Value

SearchFind or create

In Zapier“Search a person by field. If there is many entity with the same value, an error will be returned.”

Looks up a person in an event by the value of any one field you name, not only the email address.

When to use it
the key shared by your tools is an id from another system, stored in a person field.
Watch out
if several people share that value, it returns an error. The editor also offers it as Register Person if search not found, the same search with creation switched on.
3

Search Single Email

SearchFind or create

In Zapier“Search a person by email. If there is many person with the same email, an error will be returned.”

Finds the person in an event who owns a given email address and hands that record to the next steps.

When to use it
right before Update Person, when the incoming data only carries an email.
Watch out
two people with the same email in the event means an error. Its find-or-create twin, Register Person if search not found, registers the person when nobody matches.

The three settings every search exposes

  1. Successful if no search results are found?
    Left as it is, a search that finds nobody stops the Zap and the steps that needed it are skipped. Switch it on and the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    Tick it and the search becomes a find-or-create (on inwink, Register Person if search not found). The setting above goes away and the fields to register the person appear.
  3. If multiple search results are found?
    Three ways out: keep the first match (the default), stop the Zap, or pass every match on. Bear in mind the two inwink person searches already return an error on duplicates.
When it breaks

When it breaks

Zapier ties no help article to inwink, so the cases below come from how Zapier itself behaves, plus the errors written into the inwink operations.

Most of these failures are quiet: the Zap stays on and does nothing, or does far too much. When a run looks wrong, our Zapier troubleshooting guide walks through the checks in order.

  • Nothing from before the Zap

    A Zap only reacts to what happens after you switch it on. Registrations, orders and answers already in inwink stay where they are; moving that backlog is a separate job.

  • The update loop

    A Zap on Person Updated that runs Update Person on the same event sets itself off again and again, and your task count drains fast. Members and companies carry the same risk.

  • Bulk imports held back

    Import a big list into an event and a trigger can return a huge batch at once. Zapier's flood protection may then hold it back rather than run every item.

  • Duplicates stop person searches

    Search Single Email and Search Person Field With Single Value return an error when several people match, so duplicate records in an event stop the Zap at that step.

  • Search by Email sees each person once

    Zapier remembers what this polling trigger has already seen, so the same person never starts the Zap twice, even if the record is still there at the next check.

  • A failed action writes nothing

    An action that does not go through costs no task, but nothing reached inwink either: a wrong Event ID or CommunityId leaves the record unwritten.
Need help

Need help automating inwink with Zapier?

A person reads every message.

FAQ

inwink and Zapier: your questions

01Is the inwink Zapier integration free?
Yes, it works on the free plan, because inwink is not a premium app. The free plan gives you 100 tasks a month and as many Zaps as you like, but each Zap is limited to two steps: one trigger and one action. As soon as you add a filter, a search such as Search Single Email, or a second action, the Zap becomes multi-step and needs a paid plan. The triggers themselves never cost anything. Plenty of simple inwink Zaps, like Person Registered followed by Create Member, fit inside the free plan without trouble.
02How many tasks does an inwink Zap use?
One task per action that completes, and nothing for the trigger. A Zap that starts on Order Added and runs a single action uses one task per order. Give it three actions and each order costs three tasks. An action that fails is not counted, and Zapier checking for new data costs nothing, however often it checks. Keep an eye on busy triggers: Person Attended to Session runs once per person and per session, so a large agenda multiplies the tasks behind it.
03Does inwink trigger Zaps in real time?
For 13 of the 14 triggers, yes. They are instant: inwink tells Zapier as soon as the registration, order, edit or answer happens, and the Zap starts right away on any plan. The one exception is Search by Email, a polling trigger, which Zapier checks at a fixed interval: every 15 minutes on Free, every 2 minutes on Professional and every minute on Team and Enterprise. In the editor, a Zap built on an instant trigger shows a lightning bolt.
04What do you need to connect an inwink account to Zapier?
An inwink account, plus access to any event or community you do not own yourself but want a Zap to touch. You link it once from the Apps page of Zapier with + Add connection, sign in to inwink in the tab that opens, then grant access. Every Zap reuses that connection afterwards. Keep the Event ID of your events close at hand: Register Person asks for it, and you read it in your inwink back-office URL rather than in a list.
05Why does Search Single Email stop the Zap with an error?
Because more than one person in the event shares that email address. Both inwink person searches, Search Single Email and Search Person Field With Single Value, refuse to choose between duplicates and return an error, so the Zap halts at that step. The fix happens in inwink: clean up the duplicate records of the event before relying on these searches. When nobody is found at all, the setting Successful if no search results are found? decides whether the Zap stops or carries on empty-handed.
06What if the inwink operation you want is missing from Zapier?
Then this integration cannot do it today. The list on this page is the full set of visible operations, read on 2026-10-06 from version inwinkCLIAPI@4.0.0: 14 triggers, 6 actions and 3 searches. There is no delete action, for example, so removing a person still happens by hand. Two routes remain: check what the inwink integration offers on Make, which has its own page on our site, or ask our team to look at your case before you build half a Zap around a gap.
07Zapier, Make or n8n for inwink?
Decide on criteria rather than a ranking. First, does each tool offer the inwink operations your process needs? On Zapier, inwink has 23 visible operations, 13 of them instant triggers. Second, how is the bill counted? Zapier counts completed actions as tasks, and the free plan covers two-step Zaps. Third, who maintains the automation once it runs? A team without technical help needs the simplest editor. Check the inwink operations on Make and n8n against those three points before committing.
Same platform

Other docs you might need on this stack.

Browse all integrations