Integrations
Connect Lynkist to the tools you already use — browse the marketplace, connect an app, and let events trigger WhatsApp messages automatically.
Integrations connect Lynkist to the other systems your business runs on — your store, your CRM, your tools — so that things happening there can trigger WhatsApp messages here, with no manual work. An order ships, a cart is abandoned, a lead is created: the integration catches the event and Lynkist acts on it.
You'll find everything under Integrations in the sidebar.
The marketplace
The Integrations page is a marketplace of available connectors. Each connector is a first-party integration built and maintained by Lynkist (not a third-party plugin), so the connection, permissions, and data handling are consistent and supported.
Each connector card shows what it does and what it can react to. Open one to see:
- Permissions requested — exactly what access the connector needs in the other app. Review this before connecting.
- Triggers — the events from that app that Lynkist can respond to.
Public API and Webhooks are the connectors available today. They are the two directions of the same job: the Public API is your code calling Lynkist — contacts, templates, messages, campaigns — with scoped API keys, a request log and your usage against the plan, all on its connector page (developer reference). Webhooks is Lynkist calling you — deliveries, reads, inbound replies, campaign lifecycle — pushed to your own endpoint (developer reference).
Shopify is rolling out — it is built, but it is not switched on for every account yet, so it may not appear in your marketplace. What it does when it reaches you is described below. The Integrations page lists everything else we're building with the quarter we expect it. If a tool you need isn't there, tell us via the Contact page.
Shopify
Shopify connects with your store, and works in both directions.
From Shopify to WhatsApp. When an order is placed, Lynkist adds or updates the customer as a contact and sends them an order template on WhatsApp. That means the confirmation reaches them in the app they already have open, and the buyer is in your contact list for later.
From WhatsApp back to Shopify. When that message is delivered, Lynkist writes a note on the order's timeline in Shopify, so your store team can see the customer was reached without leaving Shopify.
Connecting asks for your shop domain and then sends you to Shopify to approve access. Lynkist registers the webhooks it needs at that point, and removes them again if you disconnect.
Order-placed is the trigger available today. Tell us on the Contact page which store events you want next — it is the fastest way to move one up the list.
Connecting an app
The steps below apply to connectors that authorise against another app, such as Shopify. Shopify also asks for your shop domain before it sends you there. The first-party ones need no authorisation: Webhooks takes an endpoint URL directly, and the Public API is enabled by connecting it and then creating a key.
- Open the connector from the marketplace.
- Review the permissions requested.
- Click Connect and complete the authorization in the other app (you'll be sent to that app to approve access, then returned to Lynkist).
- Once connected, the integration shows as active and its triggers become available.
Connect with an account that has admin rights in the other app. A connection made with a limited-permission account may silently miss events it wasn't granted access to.
Triggers — turning events into messages
The point of an integration is automation. A connector exposes triggers — meaningful events from the source app (for example, in a store: order placed, order fulfilled, cart abandoned). You map a trigger to a Lynkist action, typically sending a template to the customer involved.
This is what powers classic WhatsApp use cases:
- Order confirmations and shipping updates the moment they happen in your store.
- Abandoned-cart nudges a set time after a cart is left.
- New-lead welcomes when a contact is created in your CRM.
Managing and monitoring
Open a connected integration to manage it — adjust its configuration, pause it, or disconnect. Each integration keeps an event log so you can see what came in from the source app and what Lynkist did with it. When something doesn't fire as expected, the event log is the first place to look.