Build Participant Object

Build a new Opsgenie participant object for use as an input value with other Opsgenie action cards.

Note

Make sure that the API key that's used to create the Opsgenie connection for this card is not team-specific. Otherwise, any input value in the Team ID or Team Name fields on this card will not override the team that's specified by a team-specific API key. It is recommended to create and manage API keys on the Opsgenie API key management page.

Options

Field Definition Type Required
Participant Type Choose one of the following options to build a participant object:
  • None: No participant object will be assembled.
  • User: Assemble an object for a user by ID or username.
  • Escalation: Assemble an escalation object by escalation ID or username.
  • Team: Assemble an object for a team by team ID or username.
 Dropdown TRUE

Input

Field Definition Type Required
Participant
Identifier Type For the option User, build an object using the User ID or Username option.

For the option Escalation, build an object using the Escalation Name or Escalation ID option.

For the option Team, build an object using the Team Name or Team ID option.

 Dropdown FALSE
Identifier String identifier, based on the Identifier Type selection, for the specified participant object type. String TRUE

Output

Field Definition Type
Participant Resulting participant object.

Example for a user object:

Copy
{
    "type":"user",
    "id":"d92b2aa1-4bc8-481b-a30e-4f19e5a27f83",
    "username":"johnathan.doe@okta.com"
}

Example for an escalation object:

Copy
{
    "type":"escalation",
    "id":"3f145401-e6f3-428f-9f3c-41b0e1d172d5",
    "name":"Team 2_escalation"
}

Example for a team object:

Copy
{
    "type":"team",
    "id":"d00f95c1-2cce-4110-adbc-2ceca786c305",
    "username":"lily.doe@okta.com"
}
 Object

Related topics

Opsgenie connector

Workflow elements

Opsgenie API overview