Resources · Zapier integration

LiveSwitch Zapier integrationAutomate LiveSwitch with Zapier.

The LiveSwitch Zapier integration gives you 14 triggers, 19 actions and 18 searches around contacts, video conversations, recordings, documents, projects and Spark runs. Here is what each one does, which ones fire instantly, what it costs, and what tends to break.

See the 51 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the LiveSwitch Zapier integration does for you

The LiveSwitch Zapier integration links your LiveSwitch account, the video communication tool your customers join without downloading anything, to Zapier, a service that chains actions between apps. A recording lands, a contact changes, a conversation is created: Zapier carries the next step for you.

Recordings filed where your team works. New Recording starts the automation as soon as a recording exists, and the next step can drop its details in your file storage or your spreadsheet. Nobody has to go fetch it.

Conversations opened from another tool. Create Conversation starts a LiveSwitch conversation from data that arrives elsewhere, with a text message sent to the contact if you choose. The invitation goes out without anyone copying a phone number.

Spark reports produced on demand. Create Conversation Spark runs a Spark template on a conversation, and Share Spark creates a public link to the finished run that you can pass on.

The most useful thing to know: eight of the fourteen triggers are instant. New Contact, New Conversation, New Document, New Recording and their four Update twins fire straight away, even on the free plan. The six triggers whose name starts with Find wait for Zapier's next check. When both exist for the same thing, pick the instant one.

What Zapier does not do here: it never deletes a contact, a conversation or a project. The only delete is Delete Spark, and it only removes a Spark run that is still queued.

If the platform choice is still open, n8n vs Zapier and Make vs Zapier lay out the criteria.

Vocabulary

Zapier vocabulary in one minute

Seven words return on every line of this page. Here they are once, in plain English.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time the starting event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for that event and nothing else.
Action
What the Zap does once started: the step that writes, sends or moves something in an app on your behalf.
Task
The unit Zapier bills: one action your Zap completes successfully. The count on your plan is a count of those.
Polling vs instant
Polling: Zapier asks the app for new items on a timer. Instant: the app reports the event to Zapier the moment it happens.
Filter
A step that lets the Zap go on only when the incoming data meets your condition, and stops it otherwise.
Search step
A step that looks up something already stored in an app, so the following steps can use what it found.
Cost

What a LiveSwitch Zap really costs

LiveSwitch is not a premium app on Zapier, so it works on the free plan. You pay for actions that succeed, never for the trigger.

  • Premium appNo, works on the free plan
  • Free plan100 tasks a month, two-step Zaps
  • BilledEach successful action, never the trigger
  • LiveSwitch triggers14: 8 instant, 6 polling

Checking for new items costs nothing, however often it happens. Each action that succeeds counts once, so a three-action Zap uses three times what a one-action Zap uses; a failed action is not counted. The free plan gives 100 tasks a month, unlimited Zaps and no premium apps, but only two-step Zaps: one trigger, one action. A filter, a search or a second action makes a multi-step Zap, which needs a paid plan. The grid below is how often polling triggers are checked. It applies to the six Find triggers only, never to the eight instant ones.

Connect

Connect LiveSwitch to Zapier in three steps

  1. 01

    Open your connections

    In Zapier, open the Apps page of your account and click + Add connection. A connection is your LiveSwitch account linked once, then reused by every step that touches LiveSwitch.

  2. 02

    Pick LiveSwitch

    Search for LiveSwitch in the dialog, select it, then click Add connection. You need a LiveSwitch account, plus access to anything you do not own and want the Zap to change.

  3. 03

    Sign in and allow access

    A tab opens on LiveSwitch. Sign in and grant Zapier access to the account. The connection then shows in your list, ready for every LiveSwitch step you add.

First Zap

Your first LiveSwitch Zap: invite every new contact

GoalWhen a contact is created in LiveSwitch, open a conversation with them and send the invitation by text message.

  1. 01

    Pick the trigger

    Create a Zap, choose LiveSwitch as the app that starts it and New Contact as the event. It is instant, so the Zap starts as soon as LiveSwitch reports the contact.

  2. 02

    Test it on a real contact

    Run the test. Zapier brings back the three most recent items of the account, and you map the next step on one of them instead of on invented data.

  3. 03

    Add Create Conversation

    Add LiveSwitch as the action app with Create Conversation. Set Conversation Type, map the contact's phone or Contact ID, and set Send Text Message to yes.

  4. 04

    Test the action

    Run the action test once, on a contact you control, and check in LiveSwitch that the conversation exists and the message went out as expected.

  5. 05

    Publish

    Publish the Zap to switch it on. Contacts created before that moment are not picked up; only new ones start the Zap from here on.

Triggers

LiveSwitch triggers: instant ones and polling ones

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

1

Find All Contacts

Polling trigger

In Zapier“Find all contacts in the system.”

Reads the contact list of your LiveSwitch account page by page and starts the Zap for contacts Zapier has not seen yet. It asks for a Page and a Page Size, so you decide how much of the list each check covers.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
rarely, since New Contact covers the same ground instantly.
Watch out
Page Size defaults to 10, so a busy account may need a larger value.
2

Find All Tags

Polling trigger

In Zapier“Retrieves a list of all tags.”

Watches the list of tags defined in LiveSwitch and passes any tag it has not met before to the next step. It is how you mirror that list of tags in another tool.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
a shared spreadsheet should keep the same list of labels as LiveSwitch, without anyone updating it.
Watch out
Zapier remembers the tags it has already passed on, so only a tag it has never seen starts the Zap.
3

Find Conversations

Polling trigger

In Zapier“Finds Conversations in the system.”

Polls the conversations of the account and starts the Zap for each one it meets for the first time. It is the slower cousin of New Conversation, with the same subject and a check on a timer.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
only when New Conversation does not suit your case.
Watch out
on the free plan, a conversation can wait for the next check before anything happens.
4

Find Guided Instructions

Polling trigger

In Zapier“Retrieves guided instructions available for conversations.”

Retrieves the guided instructions available for conversations and starts the Zap when one appears that Zapier has not seen. The trigger follows that list, which LiveSwitch offers for use in conversations.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
you keep an inventory of available instructions in another tool and want it current.
Watch out
this trigger follows the list, not the use of an instruction in a conversation.
5

Find Projects

Polling trigger

In Zapier“Finds Projects in the system.”

Looks through the projects of the account and fires for each project it has not met yet. It is how a new project, with its conversations to come, can reach another app.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
each new LiveSwitch project should open a matching row or folder somewhere else.
Watch out
no instant trigger exists for projects, so the plan interval applies here whatever you do.
6

Find Spark Templates

Polling trigger

In Zapier“Finds Spark templates available to this organization.”

Follows the Spark templates available to your organization and starts the Zap when a template appears that Zapier does not know yet. Templates are what Create Conversation Spark and Create Project Spark run.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
someone must hear about a newly available template before using it in a Zap.
Watch out
it reports templates, not Spark runs; runs are found with the Spark searches.
7

New Contact

Instant trigger

In Zapier“Triggers when a new contact is created.”

Fires each time a contact is created in LiveSwitch, whether someone added it by hand or another Zap created it. The contact's details go straight to the next step.

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 new contact should land in another tool without waiting for a check.
Watch out
a Zap that creates contacts in LiveSwitch can set this trigger off again and loop.
8

New Conversation

Instant trigger

In Zapier“Triggers when a new conversation is created.”

Reacts the moment a conversation is created, whether someone opened it by hand or a Zap did. It is the entry point for anything that should follow a new video session.

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 new conversation should be logged in a sheet or announced to a colleague in another app.
Watch out
creation is not the end of the session, so recordings and documents come later through their own triggers.
9

New Document

Instant trigger

In Zapier“Triggers when a new document is created.”

Starts the Zap when a document is created in LiveSwitch. Documents belong to conversations or projects, so the next step can file them next to the rest of the case.

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 document produced during a conversation must also sit in your shared storage.
Watch out
uploaded files are found with the Find Files searches, which are a different thing from documents.
10

New Recording

Instant trigger

In Zapier“Triggers when a new recording is created.”

Fires as soon as a recording exists in LiveSwitch. The recording's details travel to the next step, which can store a link, notify someone or open a follow-up.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
whoever reviews recordings should get each one without searching LiveSwitch.
Watch out
a recording can change after it appears, and Update Recording is the trigger that follows those changes.
11

Update Contact

Instant trigger

In Zapier“Triggers when a contact is updated.”

Catches every change made to an existing contact in LiveSwitch. It complements New Contact by catching corrections made after creation, such as a new email.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
another tool keeps a copy of your contacts and must follow every change.
Watch out
pairing it with Update Contact as an action on the same records creates a loop.
12

Update Conversation

Instant trigger

In Zapier“Triggers when a conversation is updated.”

Follows each conversation after its creation, so you can react to its progress rather than only to its creation. The updated conversation is passed on to the next step.

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 tracking sheet should show the latest state of each conversation.
Watch out
a single conversation can change several times, and each change can cost an action downstream.
13

Update Document

Instant trigger

In Zapier“Triggers when a document is updated.”

Reacts when a document already in LiveSwitch is modified. Use it to keep a copy elsewhere aligned with the latest version instead of the first draft.

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 version in your storage must always match the one in LiveSwitch.
Watch out
without a filter, every small edit sends the document again, and a filter needs a paid plan.
14

Update Recording

Instant trigger

In Zapier“Triggers when a recording is updated.”

Picks up a recording again whenever it changes after its creation. It catches what New Recording cannot, since a recording can evolve once it exists.

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 to act on the final state of a recording rather than on its first appearance.
Watch out
one recording may update more than once, so plan for repeated runs on the same item.
Actions

LiveSwitch actions: what a Zap can do

LiveSwitch gives you 19 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Contact

Action

In Zapier“Creates a Contact in the system.”

Adds a contact to LiveSwitch from data collected elsewhere. Phone is the required field, and it is checked as a real phone number.

When to use it
a form on your site collects a number and the person should exist in LiveSwitch.
Watch out
a badly formatted number fails validation, so map a clean value.
2

Create Conversation

Action

In Zapier“Creates a Conversation in the system. For LiveConversation and RecordingRequest types, you must specify at least Phone number or Contact ID (or both).”

Opens a conversation and can text the contact an invitation. Conversation Type and Send Text Message are required.

When to use it
a request booked in another tool should turn into a video session invite.
Watch out
live conversations and recording requests need at least a Phone number or a Contact ID.
3

Create Conversation Spark

Action

In Zapier“Creates a Spark run for a conversation.”

Runs a Spark template against one conversation. It needs the Conversation ID and the Spark Template, and can create a public share link.

When to use it
every finished conversation should produce the same report.
Watch out
picking a template may reveal extra input fields to fill.
4

Create Project

Action

In Zapier“Creates a Project in the system.”

Creates a project in LiveSwitch, the level above conversations that searches and Sparks can target. Only Name is required.

When to use it
a new case opened in another app should get its own LiveSwitch project.
Watch out
give projects distinct names, or searching for them later gets confusing.
5

Create Project Spark

Action

In Zapier“Creates a Spark run for a project.”

Applies a Spark template to a whole project, using the Project ID and the Spark Template.

When to use it
you want a report at project level rather than one per conversation.
Watch out
tick Create Public Share Link only if the report can be seen by anyone holding the URL.
6

Create Tag

Action

In Zapier“Creates a new tag in the system.”

Adds a tag to the LiveSwitch list, from a Tag Name of 20 characters at most.

When to use it
a category created elsewhere should exist as a LiveSwitch tag too.
Watch out
a longer name is rejected, so shorten it in an earlier step if needed.
7

Delete Spark

Action

In Zapier“Deletes a queued Spark run by ID.”

Removes a Spark run that is still queued, from its Spark ID. It is the only delete action of this app.

When to use it
a run was launched by mistake and should not complete.
Watch out
it targets queued runs; a finished report is not what it removes.
8

Find Conversation by ID

Action

In Zapier“Finds a conversation in the system using its unique ID.”

Fetches one conversation from its Conversation ID and hands its details to the following steps. Zapier lists it among the actions, not the searches.

When to use it
an earlier step carries only the ID and you need the rest.
Watch out
as an action, it counts as a task when it succeeds.
9

Find Document by ID

Action

In Zapier“Finds a document in the system using its unique ID.”

Retrieves a single document from its Document ID so later steps can use its content.

When to use it
a trigger gives you a document ID and the next app needs the document itself.
Watch out
it reads one document only; for all of a conversation's documents, use the searches.
10

Find Form by ID

Action

In Zapier“Finds a form in the system using its unique ID.”

Looks up a LiveSwitch form from its Form ID and returns it to the Zap.

When to use it
you need the form definition before reading what someone submitted.
Watch out
no trigger hands out form IDs, so they must come from data you already hold.
11

Find Form Submission by ID

Action

In Zapier“Finds a form submission in the system using its unique ID.”

Reads one form submission from its Form Submission ID and passes the answers on.

When to use it
the answers of a submission should reach another tool.
Watch out
without the submission ID in an earlier step, there is nothing to look up.
12

Find Project by ID

Action

In Zapier“Finds a project in the system using its unique ID.”

Brings back one project from its Project ID, with its details for the steps that follow.

When to use it
an earlier step carries only a Project ID and the next one needs the project's name.
Watch out
each successful lookup counts as a task.
13

Find Recording by ID

Action

In Zapier“Finds a recording in the system using its unique ID.”

Fetches one recording from its Recording ID.

When to use it
an earlier step carries only a Recording ID, and you need the recording itself to store or share it.
Watch out
to list every recording of a conversation, the Find Recordings searches fit better.
14

Get Current User (Me)

Action

In Zapier“Gets the current user information based on the access token.”

Returns the user behind the current connection, read from the access token.

When to use it
you want to check which LiveSwitch account a Zap is acting as, or stamp that user in a log.
Watch out
it describes the connected user, not the contact of a conversation.
15

Get Organization Settings

Action

In Zapier“Gets the organization settings for the currently authenticated organization.”

Reads the settings of the organization you are connected to.

When to use it
you want to confirm a setting such as email invitations before a step depends on it.
Watch out
it reads settings only; changing them still happens in LiveSwitch itself.
16

Share Spark

Action

In Zapier“Creates a public share URL for an existing Spark run.”

Creates a public share URL for an existing Spark run, from its Spark ID.

When to use it
a completed report must be sent to someone outside LiveSwitch.
Watch out
anyone with the link can open the report, so share it with care.
17

Update Contact

Action

In Zapier“Updates an existing Contact in the system.”

Changes an existing contact, identified by its Contact ID, the one required field.

When to use it
another tool holds a corrected email and LiveSwitch should follow.
Watch out
get the Contact ID from a trigger or a search; the name alone is not enough.
18

Update Project

Action

In Zapier“Updates an existing Project in the system.”

Edits a project that already exists, from its Project ID.

When to use it
a case renamed in another tool should carry the same name in LiveSwitch.
Watch out
without the right Project ID from an earlier step, the action has nothing to update.
19

Update Tag

Action

In Zapier“Updates an existing tag in the system.”

Renames an existing tag. Tag ID and the new Tag Name are both required, with 20 characters at most.

When to use it
a label changed in another app must change in LiveSwitch too.
Watch out
Find All Tags gives you the Tag ID to map.
Searches

LiveSwitch searches: find what already exists

18 search steps look for data that already exists in LiveSwitch, so a later step can use it.

A search step sits at the bottom of the action event list, under the SEARCH heading. It looks up existing items and passes them on. Three settings decide what happens when the result is not the one you expected.

1

Find All Tags

Search

In Zapier“Retrieves a list of all tags.”

Returns the tags defined in LiveSwitch, in the middle of a Zap rather than as a starting point.

When to use it
before Update Tag, to get the Tag ID of the label you want to rename.
Watch out
the trigger with the same name is a different operation that starts Zaps.
2

Find Contact by Phone

SearchFind or create

In Zapier“Finds a contact in the system using their phone number.”

Finds a contact from a phone number, with Page and Page Size to set.

When to use it
a caller's number arrives and you want their LiveSwitch record.
Watch out
the editor also shows Find or Create Contacts. It is this same search with the create box ticked, not an extra operation.
3

Find Contact by ID

Search

In Zapier“Finds a contact in the system using their unique ID.”

Retrieves a contact from its ID, so you get the full record behind an identifier.

When to use it
a conversation carries a Contact ID and the next step needs the email.
Watch out
Page and Page Size are required here too, even for a single contact.
4

Find Conversations

Search

In Zapier“Finds Conversations in the system.”

Looks up existing conversations from within a Zap and passes them to the following steps.

When to use it
before creating a conversation, to check one is not already open.
Watch out
the trigger of the same name starts Zaps; this search only answers inside one.
5

Find Conversation Sparks

Search

In Zapier“Finds Spark runs for a conversation.”

Lists the Spark runs made for one conversation, from its Conversation ID, so a later step can share or file what is already there.

When to use it
you want the report already produced instead of running a new one.
Watch out
it finds runs, it does not start one.
6

Find Documents by Conversation

Search

In Zapier“Finds all documents for a conversation.”

Gathers every document attached to a conversation, from the Conversation ID, and hands them to the next step.

When to use it
a conversation ends and its documents should be archived together.
Watch out
set the multiple-results setting, or only the first document moves on.
7

Find Documents by Project

Search

In Zapier“Finds all documents for a project.”

Collects all documents of a project from the Project ID.

When to use it
a project closes and you want its documents in one place.
Watch out
a project can hold many documents, and each action you run on them is a task.
8

Find Files by Conversation

Search

In Zapier“Finds all files (uploaded documents) for a conversation.”

Returns the files uploaded in a conversation, as opposed to its documents, from the Conversation ID.

When to use it
the files received in a conversation belong in your storage.
Watch out
files and documents are separate searches, so pick the right one.
9

Find Files by Project

Search

In Zapier“Finds all files (uploaded documents) for a project.”

Lists the uploaded files across a project, from its Project ID.

When to use it
every file received for one case should be copied out in a single run.
Watch out
without the Project ID from an earlier step, the search has no target.
10

Find Guided Instructions

Search

In Zapier“Retrieves guided instructions available for conversations.”

Pulls the guided instructions available for conversations into a running Zap, so a later step can use them.

When to use it
a later step needs to reference an instruction when it opens a conversation.
Watch out
this is the search, distinct from the trigger that carries the same name.
11

Find Projects

Search

In Zapier“Finds Projects in the system.”

Searches the existing projects of the account and returns what it finds.

When to use it
before Create Project, to avoid opening the same project twice.
Watch out
it is not a find-or-create, so creating the missing project takes its own action.
12

Find Project Sparks

Search

In Zapier“Finds Spark runs for a project.”

Brings back the Spark runs made for a project, from the Project ID.

When to use it
you want the latest project report to share with Share Spark.
Watch out
a run still in the queue may not have its report yet.
13

Find Recordings by Conversation

Search

In Zapier“Finds all recordings for a conversation.”

Brings back all recordings of one conversation, from its Conversation ID.

When to use it
a session produced several recordings and you want all of them filed.
Watch out
choose to pass every match on, or you only get the first recording.
14

Find Recordings by Project

Search

In Zapier“Finds all recordings for a project.”

Gathers all the recordings of a project, from its Project ID.

When to use it
a project review needs every recording listed in one sheet.
Watch out
a large project returns many recordings, and each one handled after counts as a task.
15

Find Snapshots by Conversation

Search

In Zapier“Finds all snapshots for a conversation.”

Returns the snapshots taken during one conversation, from the Conversation ID, ready for the next step.

When to use it
the snapshots of a conversation should be attached to the matching record.
Watch out
snapshots, files and recordings each have their own search.
16

Find Snapshots by Project

Search

In Zapier“Finds all snapshots for a project.”

Collects all the snapshots of a project, from its Project ID.

When to use it
a closing report on a case should include every snapshot.
Watch out
the Project ID has to come from a trigger or an earlier search.
17

Find Spark by ID

Search

In Zapier“Finds a Spark run by ID.”

Retrieves one Spark run from its Spark ID and hands it to the next step, which can then share or file it.

When to use it
a Zap started a run earlier and a later Zap must check its result.
Watch out
keep the Spark ID somewhere, since no trigger reports new runs.
18

Find Spark Templates

Search

In Zapier“Finds Spark templates available to this organization.”

Looks up the Spark templates available to your organization during a Zap.

When to use it
a step must pick the right template before running a Spark.
Watch out
the trigger with the same name watches for new templates; this one only looks.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there. Switched on, the Zap continues with nothing in hand.
  2. Create X if it doesn't exist yet?
    Ticking it turns a search into find-or-create: it then asks for the fields needed to create the missing item.
  3. If multiple search results are found?
    Keep the first match (the default), stop the Zap, or pass every match on at once.
When it breaks

When a LiveSwitch Zap breaks

Zapier attaches no help article to LiveSwitch, so the cases below are the general ones. With eight instant triggers, some of them show up fast.

Most broken LiveSwitch Zaps fit one of these four cases. If yours does not, the Zapier troubleshooting page is the next stop.

  • Old recordings never arrive

    A Zap only reacts to what happens after it is switched on. Recordings, contacts and documents created earlier stay where they are; moving that history is a separate job.

  • The Zap keeps restarting itself

    A Zap that writes where its trigger watches loops. Update Contact as an action under an Update Contact trigger is the classic case, and it burns the task count fast.

  • A bulk import is held back

    When a polling trigger suddenly returns a huge batch, after an import for instance, Zapier's flood protection can hold those items back instead of running them all.

  • An item does not run twice

    On a polling trigger, Zapier remembers what it has already seen. The same contact or project will not start the Zap a second time; that is by design.
Need help

Need help automating LiveSwitch with Zapier?

A person reads every message.

FAQ

LiveSwitch Zapier integration: common questions

01Is the LiveSwitch Zapier integration free?
Yes, within the limits of the free plan. LiveSwitch is not a premium app, so it works there, with 100 tasks a month and unlimited Zaps. The catch is the two-step rule: one trigger, one action. A Zap that looks up a contact by phone before opening a conversation, or that adds a filter, is multi-step and needs a paid plan. You also need your own LiveSwitch account, since Zapier only connects to it.
02How many tasks does a LiveSwitch Zap use?
One task per action that succeeds. The trigger is free, and so are Zapier's checks on the six polling triggers, however often they run. A Zap that opens a conversation for each new contact uses one task per contact. Note that the Find by ID operations sit among the actions, so a successful lookup with Find Recording by ID counts as a task too. A failed action is never counted against your plan, so a test that breaks costs nothing.
03Does LiveSwitch trigger Zaps in real time?
For eight of its fourteen triggers, yes. New Contact, New Conversation, New Document, New Recording and the four Update triggers are instant: LiveSwitch tells Zapier as soon as the event happens, whatever your plan. The six Find triggers are polling: Zapier checks every 15 minutes on the free plan, every 2 minutes on Professional, every minute on Team and Enterprise. When you can choose between the two kinds, build on the instant trigger.
04What does it take to connect LiveSwitch to Zapier?
A LiveSwitch account, and access to anything you do not own that the Zap should change. In Zapier, open the Apps page, click + Add connection, pick LiveSwitch, sign in on the tab that opens and grant access. The connection is saved once and reused by every LiveSwitch step, in every Zap you build afterwards. Once it is in place, testing a trigger brings back the three most recent items of your LiveSwitch account, which tells you the link works.
05Why does a LiveSwitch conversation invite never reach the contact by email?
Because the email invitation of Create Conversation depends on two things. The step needs an email or a Contact ID, and the Allow Email Invitations option has to be enabled in your organization settings. If either is missing, the email does not go out. Get Organization Settings can read those settings inside a Zap, and the text message invitation, controlled by Send Text Message, is a separate choice that works on its own.
06What if the LiveSwitch operation you need does not exist?
Then Zapier cannot do it with this app: the fourteen triggers, nineteen actions and eighteen searches are the whole menu. Before giving up, check whether a search followed by an action covers the need: many gaps close that way, at the price of a multi-step Zap on a paid plan. Otherwise, compare what other automation platforms offer for LiveSwitch before building a workaround. A Find by ID action that brings back a full record from a bare ID often fills the gap.
07Zapier, Make or n8n for LiveSwitch?
Decide by criteria rather than by brand. Zapier offers 14 LiveSwitch triggers, 8 of them instant, plus 19 actions and 18 searches, and eight of those triggers fire straight away even on the free plan. Look at your volume, since every successful action is billed. Look at how many steps your scenarios need, since anything beyond two requires a paid plan. Then compare those points across the three tools, with your own scenarios in hand.
Same platform

Other docs you might need on this stack.

Browse all integrations