Get My Details

webex.get_me
ActionChat & messagingconnection required

Calls the Cisco Webex API with the connection's credentials.

Fetch the person or bot the connection's token belongs to.

Connection

Required
Yes — the node will not save without one
Auth type
Bearer token
Providers
Cisco Webex
Secret shape
the Webex access token, or {"access_token": "…"}
Resolved by
config.connection_id, else node.connection_id

Configuration

This node takes no configuration beyond its connection.

Output

One shape.

result

FieldTypeExample
id
The person id — pass it to webex.create_membership.
string—
emails
The person's email addresses; the first is the primary one.
array—
display_name
The person's display name.
string—
first_name
The person's first name.
string—
last_name
The person's last name.
string—
avatar
URL of the person's avatar image.
string—
org_id
Id of the person's organisation.
string—
type
'person', 'bot' or 'appuser'.
string—
status
Presence, e.g. active, meeting, DoNotDisturb — when shared.
string—
timezone
The person's timezone, e.g. America/Denver.
string—
last_activity
When they were last active (ISO-8601).
string—
created
When the account was created (ISO-8601).
string—
{
  "avatar": "",
  "created": "",
  "display_name": "",
  "emails": [],
  "first_name": "",
  "id": "",
  "last_activity": "",
  "last_name": "",
  "org_id": "",
  "status": "",
  "timezone": "",
  "type": ""
}

Notes

  • The cheapest way to prove a token works and to learn the id it acts as — the same call the connection self-test makes.

See Get My Details run in a workflow.

In a technical demo we add the Cisco Webex connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.