Resources · Make integration

Cisco Webex Make integrationAutomate Cisco Webex with Make.

Can Make post, file and tidy your Webex spaces while your team keeps talking? The Cisco Webex Make integration gives you 5 instant triggers, 20 actions and 5 searches over rooms, messages, teams and cards. This guide connects your account and walks you through a first working scenario.

Try the Cisco Webex integration on Make See the 30 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Cisco Webex Make integration do for you?

The Cisco Webex Make integration links your Webex account to Make, a no-code tool where you build scenarios: automations made of modules, each module being one brick such as a trigger, an action or a search. Webex can start a scenario the moment a message, room or card changes, and Make can also write back into Webex.

A form that answers itself. When someone fills in a card inside a space, Watch Attachment Actions starts the scenario and Create a Message confirms the request in the right room, so nobody has to acknowledge it by hand.

Spaces that open with the project. A new deal or ticket in another app can call Create a Room, then Create a Membership for each person involved. The room exists before the kickoff call, with the right people already inside.

A cleaner workspace. List Rooms and List Team Memberships give you an inventory you can review, and Delete a Membership removes someone who left the project. Deletions cannot be undone, so test them on a sandbox room first.

The public directory lists no limits for this app, and there is no official connection guide beyond the standard Make flow. When a Webex feature has no module, Make an API Call reaches the Webex API with the same connection. If you also work with n8n, the Cisco Webex n8n integration covers the same app, and n8n vs Make lays out how the two tools differ. For a guided start, the Make training builds scenarios like these step by step.

Connect

How do you connect Cisco Webex to Make?

01
Add a Cisco Webex module
In your scenario, click the +, search for Cisco Webex and pick any module. Then click Create a connection. A connection is your Webex account linked to Make once and reused by every Cisco Webex module you add later.
02
Name it and authorize Make
Give the connection a clear name if you like, for example the account it belongs to. Make then sends you to Webex to authorize access, or asks for the key Webex gives you, depending on the connection type offered.
03
Save and check the lists
Click Save. Back in the module, Make can now read your Webex data, so the fields that expect a room or a team show what your account can see. If those lists stay empty, the account you authorized is probably not the one you meant.

First scenario

Build your first scenario with Cisco Webex

GoalWhen someone submits a card in a Webex space, Make posts a confirmation message in the room you choose.

01
Create the scenario
Open the Scenarios page, create a new scenario and click the big +. That first slot holds the trigger, the module that decides when everything starts.
02
Add Watch Attachment Actions
Search for Cisco Webex, pick Watch Attachment Actions and select your connection. It is an instant trigger: Webex calls Make through a webhook as soon as a card is submitted.
03
Add Create a Message
Click the + on the right of the trigger and add Create a Message. Choose the room to post in, then write the text and map details from the trigger into it.
04
Test with Run once
Click Run once, then submit a test card in Webex. Each module shows the bundles it received, a bundle being one item passed along, here one submission. Check the message landed in the room.
05
Switch it on
Save and turn the scenario on. Each module run on one bundle is an operation, the unit Make counts on your plan, so this scenario uses two per submitted card.

Triggers

Which Cisco Webex triggers start a scenario?

5 modules start a scenario when something happens in Cisco Webex. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Cisco Webex as soon as it happens.

Cisco Webex1Watch Attachment Actions

Watch Attachment Actions

Instant trigger

In Make“Triggers when an attachment card is submitted.”

Turns every submitted card into a starting point: the moment someone fills in and sends an attachment card in a space, your scenario receives that submission and can act on it.

How it fires

instant, Webex calls Make through a webhook as soon as it happens.

When to use it

you post approval or request cards in a team space and want each answer logged, routed or confirmed without anyone copying it by hand.

Watch out

it only sees cards being submitted. Posting the card in the first place is a separate job, done with a message.

Cisco Webex2Watch Events

Watch Events

Instant trigger

In Make“Triggers by all events from attachment actions, memberships, messages and rooms.”

Gives you one entry point for almost everything that moves in Webex: card submissions, memberships, messages and rooms all arrive through the same trigger, so a single scenario can react to all of them.

How it fires

instant, Webex calls Make through a webhook as soon as it happens.

When to use it

you want an audit trail of activity sent to a sheet or a log, whatever kind of change it is.

Watch out

busy accounts produce many events, and each one costs operations. When you only care about messages or rooms, the dedicated trigger is lighter.

Cisco Webex3Watch Memberships

Watch Memberships

Instant trigger

In Make“Triggers when memberships are added, updated or deleted.”

Tells your scenario who joins, changes role in or leaves a room. You get a bundle each time a membership is added, updated or deleted, which is the raw material for onboarding and access tracking.

How it fires

instant, Webex calls Make through a webhook as soon as it happens.

When to use it

a newcomer lands in a client room and should get a welcome note, or your security team wants a record of every departure.

Watch out

additions, updates and deletions all come through, so decide which ones your next module should actually handle.

Cisco Webex4Watch Messages

Watch Messages

Instant trigger

In Make“Triggers when messages are added or deleted.”

Hands every new or deleted message to your scenario, so conversations in Webex can feed a ticket tool, a CRM note or an archive without anyone forwarding them.

How it fires

instant, Webex calls Make through a webhook as soon as it happens.

When to use it

a support room where each question should become a ticket, or a decisions channel you want mirrored somewhere searchable.

Watch out

if the same scenario posts back with Create a Message, its own reply counts as a new message and can restart the scenario. Post the reply to a different room than the one you watch.

Cisco Webex5Watch Rooms

Watch Rooms

Instant trigger

In Make“Triggers when rooms are added or updated.”

Lets your scenario know whenever a room is created or updated, so the rest of your stack keeps an accurate picture of the spaces your organization uses.

How it fires

instant, Webex calls Make through a webhook as soon as it happens.

When to use it

you keep a register of project spaces in a sheet or database and want each new room added to it the moment it appears.

Watch out

updates arrive through the same trigger as creations, so a renamed room produces a bundle too. Plan for both cases in the next module.

Modules

What can Make do in Cisco Webex?

Cisco Webex gives you 25 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Cisco Webex1

Create a Membership

Action

In Make“Adds a person to a room by its ID or email address.”

Puts a person into a room for you, using their Webex ID or simply their email address, so access follows your process instead of someone's memory.

When to use it

a deal is signed in your CRM and the account manager, the client and the delivery lead should all be in the project room.

Watch out

this adds people to a room. To add someone to a team, use Create a Team Membership.

Cisco Webex2

Create a Message

Action

In Make“Posts a new message by the room ID or person ID.”

Posts a message in Webex on your behalf, either in a room or directly to one person, so alerts and confirmations arrive where your team already reads.

When to use it

a payment fails, a form comes in or a build breaks, and the right people should hear about it in their space rather than by email.

Watch out

pair it carefully with Watch Messages on the same room, or your scenario may answer itself in a loop.

Cisco Webex3

Create an Attachment Action

Action

In Make“Creates a new attachment action by the message ID.”

Records a response to a card that is already posted, pointing to it by the message ID. Your scenario can answer a card programmatically, the same way a person would submit it.

When to use it

an approval decided in another tool should be reflected on the card waiting in Webex.

Watch out

you need the ID of the message carrying the card, usually mapped from an earlier module such as Create a Message or List Messages.

Cisco Webex4

Create a Room

Action

In Make“Creates a new room.”

Opens a new Webex space from your scenario, so every project, incident or client gets its own room without anyone clicking through the app.

When to use it

a new support escalation or onboarding starts in another tool and deserves a dedicated conversation from minute one.

Watch out

the room starts empty. Chain Create a Membership after it to invite people, mapping the room ID this module returns.

Cisco Webex5

Create a Team

Action

In Make“Creates a new team.”

Sets up a new Webex team straight from your scenario, so each new group starts the same way.

When to use it

a new department, office or long client account needs its own structure, created the same way every time from your HR or CRM data.

Watch out

a team on its own does not add anyone. Follow it with Create a Team Membership for each person who should be part of it.

Cisco Webex6

Create a Team Membership

Action

In Make“Adds a person to a team by its ID or email address.”

Adds someone to a team using their ID or email address, so the whole team is covered in one step, not room by room.

When to use it

a new hire joins the sales team in your HR tool and should appear in the sales team in Webex on day one.

Watch out

team membership and room membership are separate modules. Pick this one only when the target is a team.

Cisco Webex7

Delete a Membership

Action

In Make“Removes a person from a room by its ID.”

Takes a person out of a room, identified by the membership ID, so access closes as soon as the reason for it ends.

When to use it

a contractor's mission ends or a client relationship closes, and they should leave the project room automatically.

Watch out

it needs the membership ID, not the person's email. Find it first with List Memberships, and remember a removal is not undone by the scenario.

Cisco Webex8

Delete a Message

Action

In Make“Removes a message by its ID.”

Removes a message from Webex by its ID, useful when an automated post was wrong or is no longer relevant.

When to use it

a temporary alert, such as an outage notice, should disappear once the incident is marked resolved elsewhere.

Watch out

there is no undo. Store the message ID when you post it with Create a Message so you delete exactly the right one later.

Cisco Webex9

Delete a Room

Action

In Make“Removes a room by its ID.”

Deletes an entire Webex room by its ID, so short-lived spaces do not pile up in everyone's sidebar.

When to use it

rooms your scenario opened for single events or incidents should go once the related record is archived.

Watch out

this is the most destructive module of the app and it cannot be reversed. Test it on a throwaway room and double-check which ID you map.

Cisco Webex10

Delete a Team

Action

In Make“Removes a team by its ID.”

Removes a Webex team by its ID when the structure it represents no longer exists.

When to use it

a temporary task force or a finished client program had its own team, and you want the workspace to reflect what is actually active.

Watch out

the deletion is final. Find the right ID with List Teams first, and keep a human approval step before this module if the decision matters.

Cisco Webex11

Delete a Team Membership

Action

In Make“Removes a person from a team by its ID.”

Removes a person from a team by the team membership ID, closing their place in the group without touching the team itself.

When to use it

someone changes department in your HR system and should leave their former team in Webex at the same time.

Watch out

you need the team membership ID. List Team Memberships returns it for everyone in the team, so filter down to the right person before deleting.

Cisco Webex12

Get a Membership

Action

In Make“Retrieves the details of a membership by its ID.”

Fetches the full details of one room membership from its ID, so later modules can check who it concerns and how it is set up.

When to use it

Watch Memberships told you something changed and you want the current state before deciding whether to notify anyone.

Watch out

it reads one membership you already know. To discover memberships in a room, List Memberships is the right start.

Cisco Webex13

Get a Message

Action

In Make“Retrieves the details of a message by its ID.”

Reads one specific message by its ID and passes its details to the rest of your scenario.

When to use it

a card submission or an event points to a message, and you need that message's content to write a ticket, a note or a summary.

Watch out

it needs an ID you already have. To find messages in a room, start with List Messages.

Cisco Webex14

Get an Attachment Action

Action

In Make“Retrieves the details of an attachment action by its ID.”

Retrieves one card submission from its ID, giving your scenario the answers someone entered in the card.

When to use it

Watch Events delivers a mix of activity, and for card submissions you want the full response before filing it in a sheet or CRM.

Watch out

it works from an ID you already have. It does not search submissions, so it always comes after a trigger or another module.

Cisco Webex15

Get a Room

Action

In Make“Retrieves the details of a room by its ID.”

Pulls the details of a single room from its ID so you can reuse them later in your scenario, in a message, a record or a report.

When to use it

a message arrives with only a room ID and you want the room's name to label a ticket or an alert properly.

Watch out

one ID, one room. For several rooms at once, List Rooms returns them in a single step.

Cisco Webex16

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Sends any authorized request to the Webex API with the connection you already set up, which covers what the other modules of this app do not.

When to use it

you need a Webex feature missing from the list, and you are comfortable reading the Webex API documentation to write the request.

Watch out

this is the one technical module here. Test it with Run once and read the response bundle before relying on it.

Cisco Webex17

Update a Membership

Action

In Make“Updates the permissions of a membership by its ID.”

Changes the permissions of someone already in a room, found by membership ID, without removing and re-adding them.

When to use it

a team member becomes the project owner and should get different permissions in the room as their role changes in your project tool.

Watch out

it adjusts permissions only. To move a person to another room, combine Create a Membership and Delete a Membership instead.

Cisco Webex18

Update a Room

Action

In Make“Updates a room by its ID.”

Edits an existing room by its ID, so a space keeps matching the project or client it was created for.

When to use it

a deal changes stage or a client renames their company, and the room in Webex should be updated to match.

Watch out

updating a room triggers Watch Rooms too. If another scenario listens to room updates, expect it to fire after this module.

Cisco Webex19

Update a Team

Action

In Make“Updates a team by its ID.”

Modifies an existing team from its ID, keeping the team's details aligned with the organization it represents.

When to use it

a department gets renamed in your HR system and the matching Webex team should be updated the same day.

Watch out

you need the team ID. If your other tools only store the name, run List Teams first and pick the match.

Cisco Webex20

Update a Team Membership

Action

In Make“Updates the permissions of a team membership by its ID.”

Adjusts the permissions of a person inside a team, identified by the team membership ID, while they stay in the team.

When to use it

someone is promoted to team lead and should get new permissions in the team, following the change recorded in your HR tool.

Watch out

this changes team-level permissions, not those in a single room. Room rights go through Update a Membership.

Cisco Webex21

List Memberships

In Make“Retrieves a list of memberships filtered by the room ID, person ID or person email.”

Returns the memberships that match a room, a person ID or a person's email, which answers "who is in this room?" or "which rooms is this person in?"

When to use it

before offboarding someone, you want every room they belong to so you can remove them one by one.

Watch out

a search can return zero, one or many bundles, and each bundle runs the modules after it once. Plan for the empty case.

Cisco Webex22

List Messages

In Make“Retrieves a list of messages filtered by criteria.”

Fetches messages that match your criteria, so you can export a conversation, build a digest or find the one post you need to act on.

When to use it

a project closes and you want its room's messages copied into your document tool as a record.

Watch out

each message comes out as its own bundle. Many messages mean many operations for every module placed after this one.

Cisco Webex23

List Rooms

In Make“Retrieves a list of rooms filtered by criteria.”

Brings back the rooms matching your criteria, a quick way to see which spaces exist before you create, rename or clean anything.

When to use it

before opening a room for a new client, check whether one already exists so your scenario does not create a duplicate.

Watch out

an empty result is a valid answer. Route that case explicitly rather than letting the next module fail.

Cisco Webex24

List Team Memberships

In Make“Retrieves a list of team members by the team ID.”

Lists everyone in a given team from its team ID, giving your scenario a roster to compare, report on or clean up.

When to use it

you reconcile the people in a Webex team with the active staff list in your HR tool and flag anyone who should not be there.

Watch out

it needs the team ID, not the team name. List Teams gets you that ID first.

Cisco Webex25

List Teams

In Make“Retrieves a list of teams.”

Retrieves the teams your connected account can see, the natural starting point for any scenario that works across teams.

When to use it

you want a regular inventory of teams in a sheet, or you need to find a team's ID from its name before updating it.

Watch out

results depend on the Webex account behind your connection. A team that account cannot see will not appear.

Need help

Need help automating Cisco Webex with Make?

A person reads every message.

FAQ

Cisco Webex and Make: common questions

01Is the Cisco Webex Make integration free?

Yes. Cisco Webex is a standard app in Make, so you can use it on the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lift those limits: a 1 minute minimum interval, unlimited active scenarios and 40 minutes of execution. Usage is counted in operations, one per module per bundle, so busy Webex triggers use more of your monthly allowance.

02What do you need to connect Cisco Webex to Make?

You need a Webex account and a Make account; the documentation lists no other prerequisite. You add any Cisco Webex module, click Create a connection, optionally name it, then authorize Make on the Webex page or paste the key Webex provides, and click Save. The connection is then reused by every Cisco Webex module you add. Modules act with the access of the account you authorized, so connect the account that can actually see the rooms and teams you want to automate.

03Do Cisco Webex triggers in Make react in real time?

Yes. All 5 Cisco Webex triggers in Make are instant: Webex calls Make through a webhook as soon as a card is submitted, a message is posted or deleted, a membership changes or a room is created or updated. There is no polling interval to wait for, unlike scheduled triggers that Make checks every 15 minutes by default on a new scenario. Instant triggers still count operations for each bundle they receive, so a busy space can consume your plan faster than you expect.

04What if the Cisco Webex module you need is missing in Make?

Use Make an API Call. It sends any authorized request to the Webex API with the connection you already created, so you can reach endpoints the listed modules do not cover. You will need to read the Webex API documentation to shape the request, and a test with Run once shows the response before you rely on it. The directory lists no limits for this app, so if a call is rejected, the answer usually sits in the Webex API documentation rather than in Make.

05Should you use Make or n8n for Cisco Webex?

It depends on the tool your team already runs. Cisco Webex exists in both, so the choice rarely comes down to the app itself. In Make you get 30 ready modules, 5 instant triggers and Make an API Call for anything missing, inside a visual editor that shows each bundle when you test. If your automations already live in n8n, its Cisco Webex node lets you stay there. Compare the modules each side offers for your exact use case before you commit.

Add a Cisco Webex module

Name it and authorize Make

Save and check the lists

Create the scenario

Add Watch Attachment Actions

Add Create a Message

Test with Run once

Switch it on

Need help automating Cisco Webex with Make?