Resources · Zapier integration

LIME Go Zapier integrationAutomate LIME Go with Zapier.

The LIME Go Zapier integration gives you 11 triggers, 5 actions and 2 searches. Every trigger is instant, so a won deal, a booked meeting or a new customer reaches your other tools straight away, and your other tools can write deals, organizations and signals back into the CRM.

See the 18 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the LIME Go Zapier integration does for you

Connecting LIME Go to Zapier means a Zap, the automation you build on Zapier, listens to your sales CRM and passes what happens there to your other tools, or the other way round. Eighteen operations are available: eleven events to react to, five ways to write into LIME Go, and two ways to look a record up.

Three results worth building. Won deals that reach the rest of the business: Won Deal fires the moment a deal closes, your spreadsheet gets a row, and Set External Key on Deal writes the row's reference back on the deal so both sides stay linked. Hot leads you can see: someone signs up elsewhere, and Create Signal raises the temperature of the company in LIME Go by the strength you choose. Churn noticed on time: Lost Customer fires when a company becomes a former customer, and the people who should know get told.

What Zapier does not do here. Nothing creates a new deal or a new organization: the two update actions only change records that exist, and they need the record's ID. The searches only find by external key, not by name. Nothing deletes anything. And Updated Deal Status ignores won and lost deals, which have their own triggers.

The good news: all eleven triggers are instant, so even on the free plan nothing waits. If you would rather hand the build to someone, see our Zapier agency page; if you are still choosing a tool, open our n8n vs Zapier comparison.

Vocabulary

Zapier vocabulary in one minute

Eight words come back all along this page. Here they are once, in plain English, so nothing slows you down later.

Zap
Your automation on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for it to happen.
Action
What the Zap does once it has started: the step that writes, updates or creates something for you.
Task
The unit Zapier bills: one action your Zap completes successfully. Your plan's allowance counts these and nothing else.
Instant trigger
A trigger the app reports itself, the moment the event happens. All eleven LIME Go triggers work this way.
Polling trigger
A trigger Zapier checks on a timer, asking the app for new items. LIME Go has none on Zapier, so no timer applies.
Filter
A step that lets the Zap carry on only when what arrived meets your condition, and stops it there otherwise.
Search step
A step that looks up a record that already exists, so the steps after it can use what it found.
Cost

What a LIME Go Zap really costs

LIME Go is not a premium app, so it works from the free plan. Zapier counts in tasks, and the trigger never costs one.

  • Premium appNo, available on the free plan
  • Free plan100 tasks a month, two-step Zaps
  • TriggerNever costs a task
  • Search stepMakes the Zap multi-step, so paid plan

Each action that goes through counts once, and one that fails is not billed. A Zap that writes an external key on every won deal spends one task per won deal. The free plan gives 100 tasks a month and Zaps of two steps only: one trigger, one action. Add a filter, a second action or a search step and the Zap becomes multi-step, which needs a paid plan. The interval grid below is for polling triggers only and does not apply here: all eleven LIME Go triggers are instant, so your plan never changes how fast a Zap starts.

Connect

Connect your LIME Go account in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. A connection is your LIME Go account linked to Zapier once, then reused by every step that talks to the CRM.

  2. 02

    Pick LIME Go

    Type LIME Go in the search box of the dialog, select it in the results and click Add connection. A new tab opens on the LIME Go side, where the sign-in itself happens.

  3. 03

    Sign in and allow access

    Log in with your LIME Go account and grant Zapier access. If the Zap will update deals or organizations owned by colleagues, check first that this account has read or write rights on them.

First Zap

Your first Zap: every won deal logged and linked

GoalWhen a deal is won in LIME Go, add it to your spreadsheet, then write the spreadsheet's reference back on the deal as an external key.

  1. 01

    Create the Zap

    Start a new Zap from your Zapier dashboard. The editor opens on an empty trigger step, waiting for the app and the event that should set everything off.

  2. 02

    Set the trigger

    Pick LIME Go, then Won Deal, and choose your connection. Test it: Zapier brings back the three most recent won deals, so you map fields on a real one.

  3. 03

    Add the spreadsheet row

    Add your spreadsheet with the action that creates a row, and map the deal's details into the columns. The row's own reference is what you write back next.

  4. 04

    Add Set External Key on Deal

    Add LIME Go again with Set External Key on Deal. Map the deal ID from the trigger, type the key name exactly as it exists in LIME Go, and map the row reference as the value.

  5. 05

    Test, then publish

    Run each step once and read what came back, then open the deal in LIME Go to see the key. With three steps, this Zap needs a paid plan. Click Publish to switch it on.

Triggers

LIME Go triggers in Zapier

11 events start a Zap when something happens in LIME Go, and 11 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Registered Negative Call

Instant trigger

In Zapier“Triggers when a negative call has been registered in a calling list.”

Goes off when a call in one of your calling lists is logged with a negative outcome. The Zap gets that call and can act on the no while it is still fresh.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you want every no recorded in a sheet, so the pattern behind them can be read later.
Watch out
only calls registered in a calling list count; a call noted elsewhere in the CRM will not start the Zap.
2

Registered Positive Call

Instant trigger

In Zapier“Triggers when a positive call has been registered in a calling list.”

The mirror of the previous one: it starts the Zap each time a call in a calling list is logged as positive. Zapier puts this trigger forward on the LIME Go page.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a good call should lead straight to a follow-up, like a task in your project tool or a message to the team.
Watch out
calls logged before the Zap was published never come through.
3

Company Worked On

Instant trigger

In Zapier“Triggers when a company gets the relation "Working On It".”

Fires when a company is given the "Working On It" relation in LIME Go, the moment someone starts actively pursuing it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you want a shared list of the accounts your team is chasing right now, fed without anyone copying names.
Watch out
it follows the relation, not activity: a company already set to Working On It does not fire again because someone calls it.
4

New Customer

Instant trigger

In Zapier“Triggers when a company gets the relation "Is A Customer".”

Starts the Zap when a company gets the "Is A Customer" relation. It marks the switch from prospect to client, which is often where other teams take over.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
the team that takes over after the sale works in another tool, and should get a record for each new customer.
Watch out
companies that were already customers when you published the Zap are never sent.
5

Updated Deal Status

Instant trigger

In Zapier“Triggers when the status of deals changes. Only true for intermediate statuses.”

Each time a deal moves from one status to another along the way, the Zap starts. It is the trigger that tracks progress through your pipeline.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
each step forward in a deal should be mirrored in a reporting sheet or announced to the team.
Watch out
it only covers intermediate statuses; a deal that is won or lost does not set it off, so use Won Deal and Lost Deal for those.
6

Won Deal

Instant trigger

In Zapier“Triggers when a deal is won in Lime Go.”

Kicks off the moment a deal is marked as won in LIME Go. Zapier highlights it on the app page, and it is the natural start of most sales Zaps.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a won deal should land in your spreadsheet or a team channel without anyone retyping it.
Watch out
it fires on the win only; the steps before it are covered by Updated Deal Status.
7

Lost Customer

Instant trigger

In Zapier“Triggers when a company gets the relation "Was A Customer".”

This one reacts when a company gets the "Was A Customer" relation, the CRM's way of saying a client has gone.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
the people who look after accounts should hear about a departure from LIME Go itself, not from a report weeks later.
Watch out
it fires only when someone sets that relation in LIME Go; a client who quietly stops buying sets nothing off.
8

Lost Deal

Instant trigger

In Zapier“Triggers when a deal is lost in Lime Go.”

A deal marked as lost in LIME Go sets this one off. Paired with Won Deal, it closes the loop on every opportunity your team works.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
lost deals belong in the same sheet as won ones, so the win rate can be read without exporting anything.
Watch out
deals lost before you published the Zap are never sent; moving that history is a separate job.
9

Booked Meeting

Instant trigger

In Zapier“Triggers when meeting is booked in Lime Go.”

Booking a meeting in LIME Go is what sets this trigger off. It catches the step where a conversation turns into a date in someone's diary.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
every booked meeting should also show up in a shared calendar or a tracking sheet.
Watch out
booking is not the meeting itself; to react once it has happened, use Reported Meeting instead.
10

Reported Meeting

Instant trigger

In Zapier“Triggers when meeting is reported using Lime Go.”

Once a meeting has taken place and someone reports it using LIME Go, this one fires. It is the moment the notes and the outcome exist.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a reported meeting should trigger the next move, like a follow-up task or an update in another system.
Watch out
a meeting that is never reported in LIME Go never reaches the Zap, however real it was.
11

Company in Touch

Instant trigger

In Zapier“Triggers when a company gets the relation "Been in touch".”

Earliest of the relation triggers, it runs when a company gets the "Been in touch" relation, the first sign of contact in the CRM.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you want a running list of new conversations, kept outside the CRM for people who never open it.
Watch out
a company already in that relation does not fire again on the next contact.
Actions

LIME Go actions in Zapier

LIME Go gives you 5 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Update Deal

Action

In Zapier“Updates a deal.”

Changes an existing deal. You point at it with its ID and fill the fields you want to change.

When to use it
a change made in another system should be reflected on the deal without anyone typing it twice.
Watch out
besides the ID, at least one other field marked as required must be set, or the step does nothing useful and fails.
2

Update Organization

Action

In Zapier“Updates an organization.”

Edits an organization already in LIME Go, identified by its ID. The fields you fill replace what was there.

When to use it
details kept up to date in another tool should flow into the matching organization in the CRM.
Watch out
the ID plus at least one other required field must be set, just like Update Deal.
3

Set External Key on Deal

Action

In Zapier“Set external key value on deal”

Writes a value into an external key of a deal, so the deal carries the reference another system knows it by.

When to use it
right after a deal is copied elsewhere, to store the other side's ID on it and keep both linked.
Watch out
the key name must already exist in LIME Go; this action fills a key, it does not create one.
4

Set External Key on Organization

Action

In Zapier“Set external key value on organization”

Does the same for an organization: it stores a value in one of its external keys, picked by name.

When to use it
a company is created in another tool and its reference there should live on the LIME Go organization.
Watch out
once the key is set, Find an Organization by External Key can find the organization by it in later Zaps.
5

Create Signal

Action

In Zapier“Creates a new signal.”

Adds a signal to a company, the trace of something a lead did, and warms that company up in LIME Go. You name the gesture and give it a strength.

When to use it
a sign-up or a visit recorded in another tool should push the company up your list of leads.
Watch out
Strength must be a number from 1 to 99; it is how much the company's temperature rises.
Searches

LIME Go searches in Zapier

2 search steps look for data that already exists in LIME Go, so a later step can use it.

A search step looks up a record that already exists and hands it to the next steps. In LIME Go, both searches work by external key, so they find what another system has already stamped. They sit at the bottom of the Action event list, under SEARCH.

1

Find a Deal by External Key

Search

In Zapier“Search for a deal using an external key or intergration id.”

Finds a deal through the value stored in one of its external keys, or through its integration id. The deal it returns can then be updated in the next step.

When to use it
another system knows the deal only by its own reference, and you need the LIME Go ID for Update Deal.
Watch out
to search on the integration id instead of a named key, the key name to type is __integrationid or __sourcenativeid.
2

Find an Organization by External Key

Search

In Zapier“Search for an organization using an external key or intergration id.”

Looks an organization up by the value of one of its external keys, or by its integration id, and passes it to the steps that follow.

When to use it
before Update Organization, when your other tool holds its own reference and not the LIME Go ID.
Watch out
both the key name and its value are required; a key that was never set on the organization finds nothing.

The three settings every search exposes

  1. Successful if no search results are found?
    Left as is, a search that finds nothing stops the Zap there and skips the steps that needed it. Switched on, the Zap goes on without the record.
  2. Create X if it doesn't exist yet?
    On apps that offer it, this box turns a search into find or create. LIME Go's two searches have no such variant, so a missing record is never created this way.
  3. If multiple search results are found?
    Three ways out when several records match: keep the first one, which is the default, stop the Zap, or pass them all on at once.
When it breaks

When a LIME Go Zap breaks

Zapier attaches no help article to LIME Go, and no limit specific to the app is documented. What goes wrong comes from the rules every Zap follows.

Four situations explain most surprises, and all of them come from the rules every Zap follows rather than from LIME Go. If one of them has you stuck, open our Zapier troubleshooting page.

  • The past is never picked up

    A Zap only reacts to what happens after you publish it. Deals won, meetings booked or customers lost before that stay out; moving them is a separate job.

  • A Zap that sets itself off

    If an action writes into the very place its own trigger watches, the Zap can restart on its own output and drain your tasks. Check this before pairing a deal trigger with Update Deal.

  • A wave of changes gets held back

    A bulk import or a mass change of relations can make a trigger send a huge batch at once. Zapier's flood protection may hold that batch back.

  • A search that comes back empty

    If the external key was never set on the record, the search finds nothing and, by default, the Zap stops there and skips the steps after it.
Need help

Need help automating LIME Go with Zapier?

A person reads every message.

FAQ

LIME Go Zapier integration: frequent questions

01Is the LIME Go Zapier integration free?
Yes, for simple Zaps. LIME Go is not a premium app, so the free plan reaches it, with 100 tasks a month and Zaps of two steps: one trigger and one action. As soon as you add a filter, a search step or a second action, the Zap becomes multi-step and needs a paid plan. Updating a deal you only know by another system's reference, for instance, takes a search and an action, so three steps. Prices change often, so check the current plan table.
02How many tasks does a LIME Go Zap use?
One per action that succeeds, and none for the trigger. A Zap that creates a signal for every sign-up spends one task per sign-up. A Zap that logs won deals in a sheet and writes the key back spends two per won deal. An action that fails is not counted. Multiply the number of actions in your Zap by how often its trigger really fires, and you have your monthly estimate.
03Does LIME Go work in real time with Zapier?
Yes. All eleven LIME Go triggers are instant: the CRM tells Zapier the moment a deal is won, a meeting is booked or a company changes relation. The polling interval that comes with each plan does not apply, so a free account gets the same speed as a paid one. In the editor, a lightning bolt marks Zaps built on this kind of trigger, which is an easy way to check.
04What does it take to connect LIME Go to Zapier?
A LIME Go account, and rights on the records the Zap will touch. You add it from the Apps page with + Add connection, sign in to LIME Go in the tab that opens and grant access. If you plan to use external keys, create them in LIME Go first: both external key actions and both searches need a key name that already exists. Without it, every run fails. Test one step before publishing.
05Why does Updated Deal Status not fire when a deal is won?
Because it only covers intermediate statuses. A deal that moves between steps of your pipeline sets it off; a deal that ends as won or lost does not. For those two outcomes, LIME Go has dedicated triggers, Won Deal and Lost Deal. A complete picture of the pipeline therefore takes three Zaps, or one Zap per outcome you care about, each starting from the right trigger. Plan the Zaps around those three outcomes.
06What if the LIME Go operation you want is not there?
Then this integration cannot do it, and no hidden setting unlocks it. On Zapier, LIME Go offers eleven triggers, five actions and two searches. Creating a new deal or organization, deleting a record or searching by name are not on the list. In that case, look at how other automation platforms handle LIME Go before you build a workaround, and weigh the effort against what the missing step brings. Sometimes keeping that step manual is simplest.
07Zapier, Make or n8n for LIME Go?
It depends on your criteria, not on a single winner. Zapier is quick to start here: eighteen operations are ready, every trigger is instant, and the editor guides you. To choose, line the three up on the same criteria: which LIME Go operations each one offers, whether its triggers arrive at once or on a check, how a run is billed, and how much of the build you want to maintain yourself.
Same platform

Other docs you might need on this stack.

Browse all integrations