Webex by Cisco

Open your browser and navigate to developer.webex.com. Sign in with your Webex account. In the top navigation, click 'My Webex Apps', then click 'Create a New App' and select 'Create a Bot'. Fill in the Bot Name (this is how it appears in Webex Spaces), the Bot Username (which becomes the email address: yourbotname@webex.bot), a description, and optionally upload a bot icon. Click 'Add Bot'. On the next page, you will see the Bot's access token. This token is shown only once — copy it immediately and store it in a secure password manager. If you navigate away without copying it, you will need to regenerate the token. Also copy the Bot's email address (displayed as username@webex.bot) — you will need this to invite the bot to Spaces. Note your bot does not need any additional scope configuration for basic messaging and meeting scheduling — the Bot token grants access to the Webex API for resources the bot is involved in. If you need to access user-level resources like personal calendars, you would need to create an Integration (OAuth 2.0) instead of a Bot, but that is a more complex setup not covered here. Before moving to Bubble, invite your new Bot to a test Webex Space by clicking the people icon in any Space, searching for the bot's email address, and adding it. This is mandatory — the bot cannot post to a Space it has not been added to.

In your Bubble app editor, click the 'Plugins' tab in the left sidebar. If you do not have the API Connector installed, click 'Add plugins', search for 'API Connector', and install the one published by Bubble. Once installed, click 'API Connector' in the left panel to open the configuration. Click 'Add another API' and name this group 'Webex'. Under 'Shared headers', click 'Add header'. Set the Key to 'Authorization' and the Value to 'Bearer YOUR_BOT_TOKEN_HERE' — replace this placeholder with your actual bot token. Check the 'Private' checkbox next to this header. This marks the token as server-side only, meaning Bubble will never send it to the browser in any page source or JavaScript bundle. Set the Content-Type shared header as well: Key 'Content-Type', Value 'application/json' (no Private checkbox needed for this one). Now add your first call. Click 'Add a call' within the Webex group. Name it 'Send Message'. Set method to POST and URL to https://webexapis.com/v1/messages. Set 'Use as' to 'Action'. In the body section, add two dynamic parameters: 'roomId' (the Space ID) and 'text' (the message content). You can also add 'markdown' as an optional parameter for formatted messages. Click 'Initialize call'. For initialization, you need to provide real values — paste your test Space's roomId and a short test message text. Click 'Initialize'. If you receive a 200 response with a message object, the call is configured correctly. If you get a 403 error, the bot is not a member of the Space you referenced — go back and invite the bot first. After initialization, expand the detected response fields to confirm Bubble parsed the id, roomId, personEmail, and text fields. Save the call.

1{
2  "api_group": "Webex",
3  "shared_headers": {
4    "Authorization": "Bearer <YOUR_BOT_TOKEN -- PRIVATE>",
5    "Content-Type": "application/json"
6  },
7  "calls": [
8    {
9      "name": "Send Message",
10      "method": "POST",
11      "url": "https://webexapis.com/v1/messages",
12      "use_as": "Action",
13      "body": {
14        "roomId": "<roomId -- dynamic>",
15        "text": "<message -- dynamic>"
16      }
17    }
18  ]
19}

With the core messaging call working, add two more calls to cover the most common additional use-cases: listing available Spaces (so users can select a destination dynamically) and creating a Webex meeting. For the List Rooms call: click 'Add a call' within the Webex group. Name it 'List Rooms'. Set method to GET and URL to https://webexapis.com/v1/rooms. Set 'Use as' to 'Data'. Leave the body empty — GET requests to /rooms return all Spaces the bot is a member of. Click 'Initialize call' with no parameters (it works without them). Bubble will detect an array of room objects with fields like id, title, type, and lastActivity. You can use this call in a Repeating Group to display Space options to an admin or bind it to a dropdown. For the Create Meeting call: click 'Add a call'. Name it 'Create Meeting'. Set method to POST and URL to https://webexapis.com/v1/meetings. Set 'Use as' to 'Action'. Add dynamic body parameters: 'title', 'start' (ISO 8601 UTC format), 'end' (ISO 8601 UTC format), and 'invitees' (an array — you may need to pass this as a JSON-formatted text string if Bubble's API Connector does not support nested arrays directly, or separate invitees with semicolons per Webex's documentation). For initialization of Create Meeting, you need to provide real ISO 8601 timestamps. Webex requires the authenticated user (your bot's organization) to have meeting scheduling permissions. If you see a 403 on meeting creation, the bot's account may not have Webex Meetings enabled — check with your Webex organization administrator. The meeting creation response includes a joinUrl and hostKey that you should store in your Bubble database for sharing with attendees. Note: the 'meeting:schedules_write' scope or 'spark:all' scope is required for meeting creation. Bot tokens automatically have the scopes they were granted at creation — if meeting creation is returning 403 for permissions (not 'Not in room'), you may need to verify your organization's Webex plan includes the Meetings API.

1{
2  "name": "Create Meeting",
3  "method": "POST",
4  "url": "https://webexapis.com/v1/meetings",
5  "use_as": "Action",
6  "body": {
7    "title": "<meeting_title -- dynamic>",
8    "start": "<start_iso8601_utc -- dynamic>",
9    "end": "<end_iso8601_utc -- dynamic>",
10    "invitees": [
11      { "email": "<invitee_email -- dynamic>" }
12    ]
13  }
14}

Now wire the API Connector calls to actual Bubble triggers. The pattern is the same whether you are sending a message or creating a meeting: a Bubble event (button click, data change, scheduled workflow) triggers a workflow action that calls the appropriate Webex API Connector action. For a simple alert on data change: select the workflow trigger you want (for example, 'When a Thing is changed' on an Order data type). Under conditions, set it to fire when Order status changes to 'Shipped'. Add a workflow action and search for 'Webex - Send Message'. You will see your initialized call appear as an action. Provide the roomId (either hardcoded from your alerts Space, or dynamic if you let users configure which Space to post to) and the message text (use 'Current Order customer_name + order has shipped!' or similar Bubble text composition. For triggering from a button: select the button element, click 'Start/Edit Workflow', add an action. If the message should be sent immediately in response to the user action, you can call the Webex API Connector action directly from a client-side workflow — the API call itself is server-side (Bubble proxies it), but the trigger is from the client. This is fine for non-sensitive operations like posting a message. For maximum security with sensitive data, route through a Backend Workflow instead. For Adaptive Cards: Webex supports rich card messages in the attachments array. To send a card, use the Send Message call but include the card JSON in the attachments parameter. Build the card JSON at adaptivecards.io/designer, then pass the serialized JSON string as the attachments body parameter. This creates interactive forms and buttons directly inside Webex Spaces — useful for approval workflows where a team member clicks 'Approve' or 'Reject' directly in Webex and the response posts back to Bubble via a Webhook.

This step covers receiving events from Webex into Bubble — for example, processing messages sent to your bot, or handling meeting-ended events. This requires Bubble's Backend Workflows, which are available on the Starter plan ($32/month) or higher. First, enable Backend Workflows in your Bubble app: go to Settings → API and check 'This app exposes a Workflow API'. Navigate to the Backend Workflows section in the left panel. Click 'New API workflow' and name it 'webex-event'. Leave the parameter detection to automatic for now — click 'Detect request data' which will display an endpoint URL in the format: https://yourapp.bubbleapps.io/api/1.1/wf/webex-event Copy this URL. Now open the Webex Developer Portal (developer.webex.com) → My Webex Apps → Webhooks → Create Webhook. Set: - Name: 'Bubble App Events' - Target URL: the Bubble endpoint URL you copied - Resource: 'messages' (to receive message events) - Event: 'created' (fires when a new message is posted to any Space the bot is in) - Leave the Secret blank for basic setup (or add a secret and verify it in your Bubble workflow for production security) Click Save. Now send a message in the Webex Space where your bot is a member. Webex will POST the event data to your Bubble endpoint. Go to your Backend Workflow in Bubble and click 'Detect request data' — Bubble will wait for an incoming request and parse its structure. If the webhook is firing correctly, Bubble will detect fields like 'resource', 'event', 'data.roomId', 'data.personEmail', and 'data.id'. Once detected, add workflow steps to process the event: for example, create a new 'Webex Message' Thing in your Bubble database, or use the detected roomId to trigger a reply via the Send Message API Connector call. RapidDev has configured this inbound/outbound bot loop pattern for multiple enterprise Bubble apps — if you need help with the Adaptive Card response flow, reach out at rapidevelopers.com/contact for a free scoping call.

1{
2  "webhook_payload_example": {
3    "id": "Y2lzY29zcGFyazovL3VzL1dFQkhPT0svNGZhOTU...",
4    "name": "Bubble App Events",
5    "resource": "messages",
6    "event": "created",
7    "data": {
8      "id": "Y2lzY29zcGFyazovL3VzL01FU1NBR0Uv...",
9      "roomId": "Y2lzY29zcGFyazovL3VzL1JPT00v...",
10      "roomType": "group",
11      "personEmail": "user@example.com",
12      "personId": "Y2lzY29zcGFyazovL3VzL1BFT1BM...",
13      "created": "2026-07-10T10:30:00.000Z"
14    },
15    "created": "2026-07-10T10:30:00.100Z"
16  }
17}

With both halves configured, run through a complete test. For the outbound path: trigger your Bubble workflow (button click, data change, or scheduled run) and verify that the message appears in your Webex Space within a few seconds. Open Bubble's Logs tab and click 'Workflow logs' to see the API call's status. A successful call shows a green status and the response body from Webex (message object with an ID). A failed call shows the HTTP status code and error message from Webex's API. For the inbound path (if configured): send a message in the Webex Space where your bot is a member and check Bubble's Logs tab for the Backend Workflow run. Expand the log to see the incoming webhook payload and any actions your workflow took. If the log does not appear within 5 seconds of sending the message, the webhook may not be registered correctly — return to developer.webex.com and verify the webhook target URL matches your Backend Workflow endpoint exactly (including the https:// prefix and no trailing slash). Common issues at this stage: the bot is not in the target Space (403 error on Send Message), the roomId is copied incorrectly (404), or an ISO 8601 date format issue on meeting creation (400 with 'Invalid date format'). Check each error against the troubleshooting section below. One additional note on the Logs tab: each API Connector call and Backend Workflow run consumes Workload Units (WU) in Bubble's post-2023 pricing. If you are running many test calls in succession, check your WU usage in Settings → Usage to ensure you are not approaching your plan's limits during development.