Connect Swimlane to Make

Make (formerly Integromat) connects to Swimlane the same way as any web service: Swimlane pushes contact events to a Make webhook, and Make calls the Swimlane public API with an HTTP module. There is no Swimlane app to install in Make.

Before you start

• A Make account.
• A Swimlane API token if your scenario needs to read or write Swimlane data (see Create an API token and make your first request).

Receive Swimlane events in a scenario

1. In Make, create a scenario and add the Webhooks app's Custom webhook trigger.
2. Create a new webhook, give it a name and copy its address.
3. In Swimlane, open Settings → Webhooks, click Add Webhook, paste the address, tick the events you need and click Create Webhook (see Set up webhooks).
4. Swimlane immediately sends a test request. Its body only holds event = test and a message, so it doesn't show Make the contact fields.
5. To teach Make the real structure, ask the webhook module to determine the data structure again, then make a real change in Swimlane, for example write a note on a contact. The event arrives within about a minute.
6. Make now knows event, timestamp and data (uuid, firstName, lastName, email, linkedinId, and changes on updates). Map them in the next modules.
7. Add a filter right after the trigger so the scenario continues only when event is not test.
8. Turn the scenario on.

Call the Swimlane API from Make

1. Add the HTTP app's Make a request module.
2. URL: for example https://api.getswimlane.com/v1/contacts/{{data.uuid}}, mapping the uuid from the webhook.
3. Method: GET.
4. Add a header named Authorization with the value Bearer wpa_your_token_here.
5. Enable response parsing so the JSON fields can be mapped.

The response adds the headline, location, companyUuids, tagIds, listUuids and pipelineStageUuid. Call GET /v1/companies/<uuid> for the company name.

Recipe: process tagged contacts on a schedule

Tagging a contact doesn't send a webhook. To hand over contacts that a rep tagged, for example "Send to CRM":

1. Start the scenario with an HTTP Make a request module: GET https://api.getswimlane.com/v1/contacts?tag_id=12&per_page=100 (find tag ids with GET /v1/tags).
2. Iterate over data and send each contact to your CRM or outreach tool.
3. Swap the tag with POST https://api.getswimlane.com/v1/contacts/<uuid>/tags and a JSON body such as {"tagIds": [18]}.
4. Schedule the scenario, for example every 15 minutes.

The tags call replaces every tag of the contact. Build the new list from the contact's current tagIds: remove the "Send to CRM" id, add your "Sent" id, keep the others.

Good to know

• Rate limit: 100 API requests per minute per Swimlane user. Large iterations can hit 429; slow them down or process fewer contacts per run.
• The token acts on the organization you last used in the Swimlane app.
• Duplicates: each member's webhooks receive the whole organization's events. Create the webhook from one account only.
• Signature: if you generated a secret, the X-Webhook-Signature header is an HMAC-SHA256 of the raw body (see Webhook payloads and signature verification). A Custom webhook parses the body for you, so strict verification is easier in your own endpoint. Otherwise, keep the webhook address private.
• The Make card in Settings → Integrations is not needed for this setup.

Troubleshooting

• The scenario only shows message in the data: the structure was learned from the test event. Determine the data structure again and trigger a real contact change.
• 401 from the HTTP module: check the header value, Bearer then the token.