Resources · Make integration

Olark Make integrationAutomate Olark with Make.

Every chat your team closes in Olark can land somewhere useful without a copy and paste. The Olark Make integration offers 1 instant trigger that receives transcripts and messages. This page shows support and sales teams how to wire it up and build a first scenario.

Try the Olark integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Olark Make integration do?

The Olark Make integration lets Olark hand its chat transcripts and messages to Make the moment they happen. Make is the tool where you build a scenario, the automation itself, as a chain of modules. On the Olark side there is exactly one module, Universal Webhook, and it starts the scenario. Everything that happens next is done by modules of other apps.

A support log that fills itself. A visitor chats with your agent, the conversation ends, and Olark sends the transcript to Universal Webhook. From there, a spreadsheet or database module of another app stores it, so the team can review conversations without opening Olark.

Warm leads for sales. An online shop often gets buying questions in chat. Each message that reaches Make can be passed to a CRM module, and the sales rep finds the context before calling back. Take a look at the Airtable Make integration if you want a simple table as the destination.

A heads-up for the right person. The trigger can also feed a messaging or email module, so a manager hears about a conversation without watching the chat console.

Two limits matter. Olark only sends webhooks from an upgraded Olark account, and the integration only listens: it cannot reply to a chat, create an operator or change anything inside Olark. Olark also exists as an n8n node; the n8n vs Make comparison covers how the two tools differ, and the Make training is there if you are new to scenarios.

Connect

How do you connect Olark to Make?

  1. 01

    Add the Universal Webhook module

    Open a new scenario, click the + and search for Olark. Pick Universal Webhook. Unlike most apps, this one needs no connection, meaning no Olark login stored in Make: the webhook itself is the link between the two tools.

  2. 02

    Create the webhook in Make

    Click Add in the module, give the webhook a name you will recognize later, and save it. Make then shows the address that Olark will call each time a chat event happens.

  3. 03

    Point Olark at that address

    In Olark, set up a webhook following Olark's own help page on webhooks, and paste the address from Make. From then on, Olark calls Make with each transcript or message instead of waiting to be asked.

First scenario

Build your first scenario with Olark

GoalWhen Olark sends a chat transcript, Make receives it and stores it in another app.

  1. 01

    Start a new scenario

    From the Scenarios page, create a new scenario and click the big +. Search for Olark and choose Universal Webhook as the first module.

  2. 02

    Create and paste the webhook

    Click Add, name the webhook and save it. Copy the address Make displays and register it as a webhook in your upgraded Olark account.

  3. 03

    Add the destination

    Click the + on the right of the Olark module and pick the app that should keep the data, such as a sheet or a CRM. Map the transcript fields that arrived from Olark into it.

  4. 04

    Test with Run once

    Click Run once, then run a test chat in Olark so it sends something. Each bundle, one item passed from module to module, shows up in the editor so you can check what Olark actually sent.

  5. 05

    Switch the scenario on

    Save and turn the scenario on. Because the trigger is instant, there is no schedule to tune: the scenario runs whenever Olark calls the webhook.

Triggers

What starts an Olark scenario?

1 module starts a scenario when something happens in Olark. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Olark as soon as it happens.

Olark1Universal Webhook

Universal Webhook

Instant trigger

In Make“Setup a webhook in Olark - see https://www.olark.com/help/webhooks”

You get each Olark chat transcript or message delivered to Make as soon as Olark sends it, ready to be passed on to any other app in your scenario. It is the only Olark module, so every Olark automation starts here.

How it fires
instant. Olark calls Make through a webhook as soon as the event happens; Make does not poll anything.
When to use it
whenever a finished conversation should create a record, a lead or an alert somewhere else.
Watch out
Olark only triggers webhooks from an upgraded account, and no connection is needed in Make, so do not look for a login step.
Need help

Need help automating Olark with Make?

A person reads every message.

FAQ

Olark and Make: common questions

01Is the Olark Make integration free?
Yes on the Make side. Olark is a standard app, available on the Free plan, which allows 2 active scenarios, files up to 5 MB and 512 MB of data transfer. Paid Make plans (Core, Pro, Teams and Enterprise) remove the cap on active scenarios and count usage in operations, one execution of one module. On the Olark side, webhooks require an upgraded Olark account, so check that plan before building anything.
02What does the Olark Make integration need to connect?
You need a Make account and an upgraded Olark account, because Olark only triggers webhooks from upgraded accounts. You do not need a Make connection, the stored login most apps ask for. You create the webhook in the Universal Webhook module, copy the address Make gives you, and register it as a webhook in Olark using Olark's help page on webhooks. The whole setup happens inside the module and in Olark's settings, with nothing to authorize.
03Does the Olark trigger in Make work in real time?
Yes. Universal Webhook is an instant trigger: Olark calls Make through a webhook as soon as a transcript or message is ready, and the scenario starts right away. That is different from scheduled triggers, which Make checks on a timer, every 15 minutes by default. With an instant trigger, the Free plan's 15 minute minimum interval does not delay anything, since nothing is polled. In practice, a transcript can reach your CRM or sheet moments after the chat closes.
04What if an Olark module is missing in Make?
Olark offers a single trigger and no action in Make, and there is no Make an API Call module for it either. So Make cannot write back into Olark: no replies, no operator changes. The usual approach is to let Olark feed Make and do the actual work in another app, such as a CRM or a sheet. For a case that goes further, the Hack'celeration team can look at it with you. The deciding factor is what you want to do with the chat data after it leaves Olark.
05Make or n8n for the Olark integration?
It really depends on the tool you already use. Olark exists in Make as the Universal Webhook trigger, and the same app often has an n8n node too. Pick the platform where the rest of your scenarios live, so your chat data sits next to the apps it feeds. On Make, check first that a single listening trigger covers what you need, since there is no action on Olark itself.
Same platform

Other docs you might need on this stack.

Browse all integrations