Resources · Make integration

inwink Make integrationAutomate inwink with Make.

Can Make pick up what happens in inwink and act on it? Yes: the inwink Make integration offers 24 modules, with 13 triggers, 8 actions and 3 searches. This guide shows event and community teams how to link their account and switch on a first scenario.

Try the inwink integration on MakeSee the 24 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the inwink Make integration do?

The inwink Make integration links your inwink account to Make so that people, orders, sessions and community records move between tools without copy and paste. In Make you build a scenario, the automation itself, out of modules, one brick per step. inwink supplies 13 scheduled triggers that watch for changes, plus 11 modules that create, update or look up records.

Welcome attendees into your community. Watch Registered Person spots each new event registrant and Create a Community member opens their profile in the inwink community, so nobody rekeys names once the event is over.

Follow up after a session. Watch Attended Session hands Make the people who sat in a talk; send them to your CRM or email tool, then use Update a Person to keep the attendee record current.

Keep finance in the loop on orders. Watch Added Order and Watch Updated Order pass each order to Make as a bundle, one item moving from module to module, so it can land in a spreadsheet or an invoicing app.

Know the limits before you build. The Make documentation for inwink lists the modules without describing them and flags its own content as AI-generated, so check each module in the editor. The triggers are listed as scheduled, and there is no universal Make an API Call module. If you are weighing another tool, read n8n vs Make; Make training covers the basics, and Make troubleshooting helps when a run fails.

Connect

How do you connect inwink to Make?

  1. 01

    Add an inwink module

    Open your scenario, click the +, type inwink and pick any module, for example Watch New Person. Make then asks for a connection, which is your inwink account linked to Make once and reused by every inwink module.

  2. 02

    Create the connection

    Click Create a connection and, if you like, give it a name that tells your accounts apart, such as the team it serves. You need an active inwink account; without one, Make has nothing to link to.

  3. 03

    Authorize and save

    Depending on what inwink asks, approve Make on the inwink authorization page or paste the key inwink gives you, then click Save. From then on, the connection sits in the dropdown of every inwink module.

First scenario

Your first inwink scenario in Make

GoalWhen a person registers for your event in inwink, Make creates a matching community member.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the large + to place your first module. The canvas stays empty until you pick an app.

  2. 02

    Add the trigger

    Search for inwink, choose Watch Registered Person and select the connection you created. Make now knows where to look for new registrants.

  3. 03

    Add the action

    Click the + on the right of the trigger, pick Create a Community member and map the registrant data from the previous module into its fields.

  4. 04

    Test with Run once

    Click Run once, then open the bubble above each module to read the bundles it received. If the new member shows up in inwink, the mapping works.

  5. 05

    Schedule and switch on

    On the first module, set the schedule, every 15 minutes by default, then switch the scenario on. Make will check inwink at that pace from now on.

Triggers

What can start an inwink scenario?

13 modules start a scenario when something happens in inwink. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by inwink as soon as it happens.

inwink1Watch Added Community Company

Watch Added Community Company

triggerIn the docs only

Every company that joins your inwink community reaches Make as its own bundle, ready to open an account in your CRM or alert the partnerships team.

How it fires
scheduled; Make asks inwink for new companies each time the scenario runs.
When to use it
sponsor firms sign up to the community and sales should hear about it without checking inwink by hand.
Watch out
it only sees additions; an edit to an existing company belongs to Watch Updated Community Company.
inwink2Watch Added Community Member

Watch Added Community Member

triggerIn the docs only

New people in your community become a list you can act on: Make receives each added member and passes the details to the next module.

How it fires
on a schedule, so a member added between two checks arrives at the next run.
When to use it
you want a welcome email sent from your mailing tool, or the person added to a newsletter segment, without waiting for an export.
Watch out
a member created by your own scenario also counts as added, so do not pair it with Create a Community member in the same flow.
inwink3Watch Added Order

Watch Added Order

triggerIn the docs only

Each new order placed through inwink lands in Make, which lets finance or ticketing tools know about it without an export.

How it fires
Make polls inwink for fresh orders at the pace set on the scenario.
When to use it
a paid event where every ticket order should appear in a spreadsheet or produce an invoice in your accounting app.
Watch out
an order that changes later will not come back through this trigger; build Watch Updated Order into a second scenario to follow later edits.
inwink4Watch Attended Person

Watch Attended Person

triggerIn the docs only

This trigger gives you the people who actually came, not just those who signed up, so follow-ups reach the right audience.

How it fires
scheduled; attendance recorded in inwink is collected at the next check.
When to use it
once the event is under way, you want attendees tagged in your CRM or sent a thank-you message, while no-shows get something else.
Watch out
it relies on attendance being recorded in inwink; if nobody logs it at your event, the trigger has nothing to return.
inwink5Watch Attended Session

Watch Attended Session

triggerIn the docs only

Session attendance turns into data you can reuse: Make learns who sat in a given talk or workshop and hands it on.

How it fires
Make reads inwink on the scenario's clock and picks up attendance logged since the previous run.
When to use it
speakers ask for their audience list, or you want to send the slides only to people who were in the room.
Watch out
one person attending several sessions produces several bundles, and each module that processes them uses an operation, which is one run of a module on one bundle.
inwink6Watch New Person

Watch New Person

triggerIn the docs only

Any person newly created in inwink shows up in Make, which makes this the broadest entry point for syncing contacts elsewhere.

How it fires
polled on the scenario's schedule rather than pushed by inwink.
When to use it
your CRM or email platform should hold every contact inwink creates, whatever event they relate to.
Watch out
it casts a wider net than Watch Registered Person; pick that one instead if you only care about people signed up to an event.
inwink7Watch Person Registered To Session

Watch Person Registered To Session

triggerIn the docs only

Sign-ups to a single session reach Make one by one, so you can plan room capacity or brief a speaker ahead of the talk.

How it fires
scheduled; new session sign-ups arrive together at each check.
When to use it
a workshop with limited seats where the organizer keeps a running count in a shared sheet, or a speaker who asked for the attendee list beforehand.
Watch out
this concerns sessions, not the event itself; for sign-ups to the whole event, Watch Registered Person is the right trigger.
inwink8Watch Registered Person

Watch Registered Person

triggerIn the docs only

You get each person who signs up to your event, the natural starting point for confirmation emails and CRM records.

How it fires
Make checks inwink for new registrants whenever the scenario's schedule comes around.
When to use it
marketing wants registrants in a nurture list, or sales wants a lead created for each company that sends people.
Watch out
the Free plan waits at least 15 minutes between two scheduled runs, so a registration can take that long to reach the next module.
inwink9Watch Survey Answered

Watch Survey Answered

triggerIn the docs only

Feedback stops sitting inside inwink: each answered survey travels to Make, ready for a spreadsheet, a dashboard or a message to the team.

How it fires
on the scenario's schedule, collecting answers submitted since the last check.
When to use it
the event team wants every answer gathered in one sheet, or account managers should read what their clients wrote.
Watch out
the documentation does not describe what an answer bundle contains, so click Run once and inspect it before mapping anything.
inwink10Watch Updated Community Company

Watch Updated Community Company

triggerIn the docs only

When a company profile changes in your community, Make hears about it and can carry the change to the tools that keep a copy of that profile.

How it fires
scheduled; Make looks for edited companies on each run.
When to use it
your CRM stores partner companies and should not drift when a sponsor updates its details in inwink.
Watch out
if the same scenario runs Update a Community Company on that record, the edit counts as a change and can start the scenario again.
inwink11Watch Updated Community Member

Watch Updated Community Member

triggerIn the docs only

Profile edits made by members, or by your team, flow to Make so the other copies of that person stay accurate.

How it fires
Make asks inwink for edited members each time the schedule starts the scenario.
When to use it
a member changes job or company, and your mailing list or CRM contact should follow without anyone spotting it by hand.
Watch out
writing back with Update a Community Member inside the same scenario creates a new edit; keep the two in separate flows.
inwink12Watch Updated Order

Watch Updated Order

triggerIn the docs only

Changes to existing orders reach Make, so a corrected order does not leave your finance records out of date.

How it fires
scheduled; edited orders are picked up on the next run, not the second they change.
When to use it
accounting keeps order lines in a spreadsheet or invoicing tool and needs the latest version, not only the first one.
Watch out
new orders are the job of Watch Added Order; use both side by side if you need the full history of each order.
inwink13Watch Updated Person

Watch Updated Person

triggerIn the docs only

When a person record changes in inwink, Make picks up the new version on the next run and can push it to every tool that relies on it.

How it fires
polled at the scenario's rhythm, like every inwink trigger on this page.
When to use it
an attendee fixes a typo in their email address, and your CRM should hold the corrected data too.
Watch out
Update a Person run in the same scenario produces an edit as well; split the flows so they do not feed each other.
Modules

What can Make do in inwink?

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

inwink1

Create a Community company

ActionIn the docs only

Adds a company to your inwink community from data held elsewhere, so the directory fills itself.

When to use it
a sponsor contract is signed in your CRM and the company should appear in the community without manual entry.
Watch out
nothing in the documentation says this module checks whether the company already exists, so guard against duplicates earlier in the flow.
inwink2

Create a Community member

ActionIn the docs only

Gives someone a place in your community straight from another source, such as an event registration or a form in another tool.

When to use it
attendees of a paid event should become community members, as in the first scenario above.
Watch out
look the person up first with one of the search modules if they might already be a member, otherwise you risk a second profile.
inwink3

Make a Community API call

ActionIn the docs only

Reaches the parts of the inwink Community API that the ready-made modules leave out, by sending a request you write yourself.

When to use it
you need a community action missing from this list and you have the inwink API reference at hand.
Watch out
the Make documentation gives no description of this module, so its behavior is inferred from its name; test it with Run once before relying on it.
inwink4

Make a Event API call

ActionIn the docs only

Opens the Event side of the inwink API for requests the other modules cannot make, judging by its name.

When to use it
an event operation you found in the inwink API reference has no module of its own here, and you want it inside a scenario.
Watch out
check the other modules first; a raw request means you build the call and read the response yourself.
inwink5

Register a person to an event

ActionIn the docs only

Signs a person up to an inwink event from another tool, which saves attendees a second form and your team a manual import.

When to use it
a lead fills in a form on your website or a deal closes in your CRM, and that person belongs on the guest list.
Watch out
every registration it creates can then be seen by Watch Registered Person; do not chain the two in one scenario.
inwink6

Search MembershipLevel by Id

SearchIn the docs only

Looks up a membership level from its identifier, so a scenario can read that level before deciding what to do next.

When to use it
a community record hands you a level Id and you want the level itself, for instance to handle your top-tier partners separately.
Watch out
as the name says, it works from the Id; if you only know the level name, start elsewhere.
inwink7

Search Single Email

SearchIn the docs only

Checks inwink against one email address, a quick way to learn whether a contact already exists before creating anything.

When to use it
right before Create a Community member or Register a person to an event, so the same person is not added twice.
Watch out
like any search, it can come back empty; decide what the scenario does when nothing is found.
inwink8

Search persons by fieldId and value

SearchIn the docs only

Finds the people whose chosen field holds a given value, which lets you look people up by something other than their email.

When to use it
you want every registrant from one organization, or everyone who gave a particular answer, before sending them something.
Watch out
it can return several people, one bundle each, and every following module then runs once per person, which adds operations.
inwink9

Update a Community Company

ActionIn the docs only

Keeps a company profile in the community in line with your source of truth, without anyone editing it by hand in inwink.

When to use it
a partner changes its address or main contact in your CRM and the community directory should show the same.
Watch out
it acts on one existing company, so a search or a trigger must say which one; new companies go through Create a Community company.
inwink10

Update a Community Member

ActionIn the docs only

Corrects or enriches a member profile from another tool, so what members see in the community matches your records.

When to use it
a member's job title changes in your HR or CRM system and their community profile should follow.
Watch out
if Watch Updated Community Member runs in the same scenario, this edit can start it again; split the two.
inwink11

Update a Person

ActionIn the docs only

Changes a person record in inwink from outside, handy when your CRM holds the master copy of contact data.

When to use it
a sales rep fixes a spelling mistake in the CRM, and the attendee record in inwink should carry the same fix.
Watch out
the module has to know which person to change; feed it the result of Search Single Email or Search persons by fieldId and value.
Need help

Need help automating inwink with Make?

A person reads every message.

FAQ

Questions about the inwink Make integration

01Is the inwink Make integration free?
Yes, inwink is a standard app in Make, so it works on the Free plan. That plan keeps 2 scenarios active, waits at least 15 minutes between scheduled runs, stops an execution after 5 minutes and handles files up to 5 MB with 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the minimum interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes per execution; usage is counted in credits, meaning operations, each month. You still need an active inwink account, whose subscription is set by inwink, not by Make.
02What do you need to connect inwink to Make?
An active inwink account is the only prerequisite the Make documentation names. The docs do not describe a connection flow specific to inwink, so you follow the generic one: add any inwink module, click Create a connection, optionally name it, then authorize Make on the inwink page or paste the key inwink supplies, and click Save. The connection is stored once and every inwink module in your scenarios reuses it. If the account has lapsed, there is nothing to authorize against, so check your subscription first.
03Do inwink triggers fire instantly in Make?
No. All 13 inwink triggers are listed as scheduled: Make asks inwink for new or changed data each time the scenario runs, instead of inwink pushing it the moment something happens. A new scenario runs every 15 minutes by default; the Free plan cannot go below 15 minutes, while paid plans go down to 1 minute. The Make directory was unavailable when this page was written, so the type comes from the module names; check the clock badge on each module in the editor.
04What if an inwink module is missing in Make?
Start with the two request modules in the list, Make a Community API call and Make a Event API call, whose names point to custom calls on the Community and Event sides of inwink; the documentation does not describe them, so test them with Run once. There is no universal Make an API Call module for inwink. If that is not enough, another app can handle part of the flow, or the team can look at your case. Make also labels its inwink documentation as AI-generated and possibly wrong, so confirm important details with inwink.
05Make or n8n for inwink?
It depends on what you need to verify first. On Make, inwink comes with 24 modules, split into 13 scheduled triggers, 8 actions and 3 searches, and it runs from the Free plan. Many apps also have an n8n node, but this page holds no verified information about an inwink node there, so confirm it exists and covers your events before choosing. Compare module by module: if the triggers and community actions you need are in the Make list above, you can start right away and test with Run once.
Same platform

Other docs you might need on this stack.

Browse all integrations