Messaging and Communication Jobs

Determines the authorization credentials that are used to connect Control-M to Atlassian Jira, as described in Atlassian Jira Connection Profile Parameters.

Rules:

• Characters: 1−30

• Case Sensitive: Yes

• Invalid Characters: Blank spaces.

Determines one of the following Atlassian Jira actions to perform:

• Create Issue: Creates a Jira issue.

• Update Issue Fields: Updates fields in a Jira issue.

• Get Issue: Retrieves data for a Jira issue.

• Add Comment to Issue: Adds a free text comment to a Jira issue.

• Get Transition Details: Retrieves data associated with all the status options for a Jira issue.

• Change Issue Status: Changes the status for a Jira issue.

Determines the ID of the Jira issue. This parameter is required for any action on an existing issue. It is not relevant for the Create Issue option.

Defines the parameters, in JSON format, to perform actions on multiple Jira fields.

The following example updates the value for multiple fields in the issue that corresponds to the Issue key:

{
  "fields": {
    "summary": "Updated summary via Postman",
    "description": "This issue was updated using the Jira REST API from Postman.",
    "labels": ["api-update", "postman-test"],
    "priority": { "id": "2" }
  }
}

Determines the status ID for a Jira issue.

Determines the authorization credentials that are used to connect Control-M to Communication Suite, as described in Communication Suite Connection Profile Parameters.

Rules:

• Characters: 1−30

• Case Sensitive: Yes

• Invalid Characters: Blank spaces.

Defines the parameters, in JSON format, that instruct Teams to perform multiple actions.

The following example defines Teams parameters in JSON format:

{
  "type": "message",
  "attachments": [
    {
      "contentType": "application/vnd.microsoft.card.adaptive",
      "content": {
        "$schema": "http://adaptivecards.io/schemas/adaptive-card.json",
        "type": "AdaptiveCard",
        "version": "1.5",
        "body": [
          {
            "type": "TextBlock",
            "text": "Workflow Alert",
            "weight": "Bolder",
            "size": "Medium"
          },
          {
            "type": "TextBlock",
            "text": "This is an adaptive card alert from my workflow.",
            "wrap": true
          }
        ]
      }
    }
  ]
}

Defines the parameters, in JSON format, that instruct Slack to perform multiple actions.

The following example sends the message, "This is a plain text section block.":

{
   "blocks": [
   {
      "type": "section",
      "text": 
      {
         "type": "plain_text",
         "text": "This is a plain text section block."
      }
   } ]
}

Defines the parameters, in simple text format, that instruct Telegram to perform multiple actions.

Rule: 1–4,096 characters.

You can add Control-M variables to the text.

Determines whether to send your Telegram message without a notification, which is useful for after-hours or non-urgent messages.

Determines whether to prevent your Telegram message from being saved or forwarded.

Determines the authorization credentials that are used to connect Control-M to Datadog, as described in Datadog Connection Profile Parameters.

Rules:

• Characters: 1−30

• Case Sensitive: Yes

• Invalid Characters: Blank spaces.

Determines one of the following actions to perform on Datadog:

• Send Event to Datadog

• Run Datadog Workflow

• Start Datadog Synthetic Test

• Create an Incident

Defines the details to send an event to Datadog, such as title, message, and alert type.

The following example defines the event details to send to Datadog:

{
   "title": "Control-M Workflow Failure",
   "text": "A Control-M workflow has failed. Immediate attention is required.",
   "aggregation_key": "controlm_workflow_failure",
   "alert_type": "error",
   "device_name": "controlm-agent-01",
   "host": "controlm-server-01",
   "priority": "normal",
   "source_type_name": "controlm",
   "tags": [
      "environment":"test",
      "source":"controlm",
      "status":"failure"
      ]
}

Defines a unique identifier assigned to a Datadog workflow to trigger.

Defines the input values required to run a Datadog workflow.

Determines the type of synthetic test to trigger in Datadog.

Value Values:

• API Test

• Browser Test

Defines the synthetic test details, including test ID and variables.

The following example defines the synthetic test details:

{
   "tests": [
      "public_id": "3bx-33h-ntp"
      ]
}

Defines the number of seconds to wait before Datadog retrieves logs or results from a synthetic test.

Default: 60

Defines the data used to create an incident, including title, severity, and associated metadata.

The following example defines the incident parameters in JSON format:

{
   "data": 
   {
      "type": "incidents",
      "attributes": 
      {
         "title": "Control-M Workflow Failure",
         "customer_impact_scope": "A critical Control-M workflow failed, affecting downstream processes.",
         "customer_impact_start": "2025-05-04T12:00:00Z"
      }
   }
}

Determines the number of seconds to wait before checking the job status.

Default: 60

Determines the authorization credentials that are used to connect Control-M to PagerDuty, as described in PagerDuty Connection Profile Parameters.

Rules:

• Characters: 1−30

• Case Sensitive: Yes

• Invalid Characters: Blank spaces.

Determines one of the following actions to perform on PagerDuty:

• Create an Incident

• Create an Incident - Detailed

• Update an Incident

• Snooze an Incident

• Incident Details

Defines a unique identifier assigned to each incident, which allows you to reference, track, and manage the incident.

Defines an email address for a valid user in your PagerDuty platform.

Defines specific parameters, in JSON format, to pass when the job executes.

The following example shows the parameters to create an incident template:

{
  "incident": {
    "type": "incident",
    "title": "The server disk is getting full on this machine",
    "service": {
      "id": "P9VABOD",
      "type": "service_reference"
    },
    "priority": null,
    "urgency": "high",
    "incident_key": "baf7cf21b1da41b4b0221008339ff123",
    "body": {
      "type": "incident_body",
      "details": "A disk is getting full on this machine."
    }
  }
}

Defines the title that describes the incident.

Defines the identifier of the service.

Determines the current urgency of the incident.

Defines the de-duplication key of the incident.