Integrations

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.

Connecting an app

1. Open the connector from the marketplace.
2. Review the permissions requested.
3. Click Connect and complete the authorization in the other app (you'll be sent to that app to approve access, then returned to Lynkist).
4. Once connected, the integration shows as active and its triggers become available.

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.

Next steps