Webex by Cisco n8n integrationAutomate Webex by Cisco with n8n.

Books a meeting on a Webex site from the data the workflow carries.

• Title: the meeting title, 128 characters at most.
• Start and End: the date and time of the start and of the end, in the format described by RFC 2445.
• Additional Fields: 19 optional fields, among them Agenda (1300 characters at most), Invitees, Send Email for the mails to host and invitees, Join Before Host Minutes whose choices are 0, 5, 10 and 15, and Site URL, which otherwise falls back to the user's preferred site.

Takes a scheduled meeting off the Webex site. Worth pairing with whatever cancels the deal or the appointment upstream, so the calendar does not keep an entry nobody will join.

• Meeting ID: the ID of the meeting, usually carried over from an earlier node with an expression such as {{ $json.field }}.
• Options: 2 fields. Host Email is the email address of the meeting host and is only used when the calling user or application has the admin-level scopes. Send Email decides whether mails go to host and invitees.

Reads a single meeting back, by ID. Usually the step just before a decision: remind, reschedule, or leave alone.

• Meeting ID: the ID of the meeting.
• Options: 3 fields. Password is the meeting password, required when the meeting is protected by one and the current user is not privileged to view it because they are neither host, co-host nor invitee. Host Email names the host, and Send Email is optional with true as its default value.

Returns a list rather than one record. No field is required here, so a node left as is already answers, and the Filters collection is where the shaping happens.

• Return All: ticked, n8n walks the API pages and brings back every meeting; unticked, Limit caps how many come back.
• Filters: 11 fields, including From and To for an inclusive window, State with its 8 values (active, ended, expired, inProgress, lobby, missed, ready, scheduled), Meeting Type (meetingSeries, scheduledMeeting, meeting) and Participant Email.

Changes an existing meeting rather than deleting it and starting over. Meeting ID says which one, Update Fields carries what moves.

• Meeting ID: the ID of the meeting.
• Update Fields: 21 fields. Start, End and Title handle a reschedule or a rename, Agenda cannot be longer than 1300 characters, Password must conform to the site's password complexity settings and gets generated at random when left empty, and Recurrence is a rule conforming with RFC 2445 that applies only to meeting series.

Posts a message in Webex. Destination sets who is on the receiving end, a room or a person.

• Destination: room or person.
• Room Name or ID: chosen from the list, or given as an ID through an expression.
• Specify Person By: email or id, alongside Person Email and Person ID.
• Text: the message, in plain text.
• Additional Fields: 3 fields, Markdown for the message in markdown format, where Text then provides alternate text for UI clients that do not support rich text, plus File and Attachments.

One field in, one message gone. This is the operation that turns a retention rule into something that actually runs, rather than a policy page nobody applies.

• Message ID: the ID of the message to delete.

Pulls one message back from Webex when the workflow only has its ID to work with, typically an ID stored earlier in a database or a spreadsheet.

• Message ID: the ID of the message to retrieve.

Lists the messages of a room, which is how a workflow gets context instead of a single line taken out of its conversation.

• Room Name or ID: required, lists messages in a room by ID, chosen from the list or given through an expression.
• Return All and Limit: all the messages, or a capped number of them.
• Filters: 4 fields, Before for messages sent before a date and time, Before Message for messages sent before a given message by ID, Parent Message ID for messages with a parent, and Mentioned Person for messages mentioning a person by ID, me standing for yourself.

Rewrites a message that is already posted. Four fields travel together here, which is unusual for this node and easy to miss on the first build.

• Message ID: the ID of the message to update.
• Is Markdown: whether the message uses markdown.
• Text: the message, in plain text.
• Markdown: the message, in Markdown format, with a maximum message length of 7439 bytes.