---
sourceDocument: Australia ServiceNow AI Platform Capabilities
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/servicenow-platform

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Create a probe activity

# Create a probe activity {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 min. de leitura

Create an activity that runs a probe on the target host that is configured to return
specific information..

## Antes de Iniciar

Role required: activity_creator or workflow_admin

## Por Que e Quando Desempenhar Esta Tarefa

For instructions on using the activity template process flow, see [create
custom activities](https://servicenow-prod.fluidtopics.net/Dtg39wkahTqlhpUmgZLYrg "You can create and update different types of custom activities in the Workflow Editor using a custom template.").

## Procedimento

1. Create a [custom
   activity](https://www.servicenow.com/docs/access?context=create-custom-activities&version=australia&pubname=australia-integrate-applications&ft:locale=en-US).  
   This action creates a custom activity using a template.
2. After setting up [general properties](https://servicenow-prod.fluidtopics.net/QMzjwyjrJWqvJ~7~1rCaSQ "The following General Property fields are common to all activity designer templates.") and [creating input
   variables](https://servicenow-prod.fluidtopics.net/g_9rwzTWMeQ5n_5NPNlctg#CreateInputVariables "Create the variables to pass into the activity in the Inputs form of the activity designer."), configure the Probe Execution Command.

   | Opção | Descrição |
   | [Map the input variables](https://servicenow-prod.fluidtopics.net/g_9rwzTWMeQ5n_5NPNlctg#t_MapAnInputVariable "After you create the input variables, map them to the fields in the Execution Command form.") | Use the variables you created to configure the command that Orchestration executes. |
   | Probe | Probe to run with this activity, from the list of probes in the system |
   | Target host | Host name or IP address of the target server for this activity. |
   | Parameters | MID Server to use, by capabilities. |
   | Required MID Server capabilities | Name-value pairs to pass to the host with this probe. You can create these parameters manually, or drag and drop input variables into the parameter fields and assign a value. |
   |-|-|

   {#t_CreateAProbeActivity__choicetable_bf3_bpv_vz}  
   Nota:  
   You can map parameter values in a test payload to variables in the Outputs tab automatically. See [automap output
   variables](https://servicenow-prod.fluidtopics.net/9dTkWlVH3YbU1Kq0sSstYQ "You can map parameter values in a test payload to variables in the Outputs tab automatically.").

## O que Fazer Depois

* Use [auto-mapping](https://servicenow-prod.fluidtopics.net/9dTkWlVH3YbU1Kq0sSstYQ "You can map parameter values in a test payload to variables in the Outputs tab automatically.") to generate outputs and parsing rules
* If you do not use auto-mapping, you can manually [create output
  variables](https://servicenow-prod.fluidtopics.net/fURMTh~zOPOBdyA_ORRVbw#t_CreateAnOutputVariable "The Outputs form in the designer contains a variable builder for creating data structures of objects and arrays.") and [create parsing
  rules](https://servicenow-prod.fluidtopics.net/XZfcwkOQGGDY51~v4ofWQA#t_CreateAParsingRule "Populate output variables defined in a custom activity with payload data returned from an inputs test on an external host or endpoint.")
{#t_CreateAProbeActivity__ul_u45_vbq_xz}

## Probe template execution parameters {#ariaid-title2}

You use execution parameters to create the input process script in the Pre Processing form.
For descriptions of the command fields, see [Configure the Probe execution command](https://servicenow-prod.fluidtopics.net/qq8Cu68eNjMUIlJYJe9_Yw#t_MapProbeVariablesToExecutionCmd "Use the input variables you created to configure the command that Orchestration executes on the target.").  
Nota:  
You must use the `executionParam.` prefix with all variables in this table.  
{#r_ProbeTemplateExecutionParameters__table_pwj_qdc_dr__entry__4}

| Name | Variable | Type | Usage |
|-|-|-|-|
| Probe | probe | Reference | The sys_id of the MID Server probe. |
| Source | source | String | Intended target host |
| Parameters | parameters | Array of JS object | Array of JavaScript objects, expressed with the `executionParam.` prefix. To add more name-value pairs to the parameters array, append them to the existing array. Create a JavaScript object with the following syntax, and add it to the `executionParam.parameter` array. This assigns additional parameters to the message: var newParameter = {"name":"parameterName","value":"parameterValue"}; executionParam.parameters.push(newParameter); |
| MidCapabilities | midCapabilities | String (comma separated) | List of required MID server capabilities. |
| ValueCapabilities | valueCapabilities | Array of hashmap | Capability values used to select the MID Server. For more information, see [MID Server capabilities](https://servicenow-prod.fluidtopics.net/6drJeseIH63daJ6elJKgqQ "MID Server capabilities define the specific functions of a MID Server within an IP address range."). If there are additional capabilities that are assigned by value, use this example to customize the MID Server selection: var valueCapability = {'NEW_MID_CAPABIILTY':'NEW_MID_CAPABILITY_VALUE'}; executionParam.valueCapabilities.push(valueCapability); |
[Tabela 1. Probe activity execution parameters]

{#r_ProbeTemplateExecutionParameters__table_pwj_qdc_dr}

## Probe template post-processing parameters {#ariaid-title3}

Use these parameters to create a post-processing script.
{#r_PbTmpltPstPPrm__table_xlq_3n5_cr__entry__4}

| Name | Variable | Type | Usage |
|-|-|-|-|
| Payload | payload | String | Contains raw payload returned from the probe. |
| Output | output | String | Contains output data returned from the probe. |
| EccSysId | eccSysId | String | Contains the reference ID associated with the ECC Queue input message. |
[Tabela 2. Probe post-processing parameters]

{#r_PbTmpltPstPPrm__table_xlq_3n5_cr}

## Configure the Probe execution command {#ariaid-title4}

Use the input variables you created to configure the command that Orchestration
executes on the target.

### Antes de Iniciar

Create the input variables you need in the Inputs form before you can advance to the Execution Command stage.

Role required:
activity_creator, admin  
Nota:  
You can test the activity connection between the MID Server and the target without having to run the acvitity in a workflow context. For details, see [test
template outputs](https://servicenow-prod.fluidtopics.net/g_9rwzTWMeQ5n_5NPNlctg#test-template-inputs "You can test the input parameters of a custom activity during its development without having to run the activity in a workflow context.").

### Procedimento

1. Drag variables from the list of inputs and drop them into command fields.  
   The system formats the variable in the proper syntax for the command.  
   Figura 1. Probe execution command
2. Complete the fields shown in the table.  
   {#t_MapProbeVariablesToExecutionCmd__table_m3w_qzb_dr__entry__2}

   | Field | Description |
   |-|-|
   | Input | Input variable builder. [Create input variables](https://servicenow-prod.fluidtopics.net/g_9rwzTWMeQ5n_5NPNlctg#CreateInputVariables "Create the variables to pass into the activity in the Inputs form of the activity designer.") to map to available fields. |
   | Probe | Probe to run with this activity, from the list of probes in the system. |
   | Target host | Host name or IP address of the target server for this activity. |
   | Required MID Server capabilities | MID Server to use, by capabilities. |
   | Parameters | Name-value pairs to pass to the host with this probe. You can create these parameters manually, or drag and drop input variables into the parameter fields and assign a value. |
   [Tabela 3. Probe execution command fields]

   {#t_MapProbeVariablesToExecutionCmd__table_m3w_qzb_dr}
3. Click Save.
4. Click Continue to advance to the Outputs stage.
{#t_MapProbeVariablesToExecutionCmd__steps_gpt_msl_s5}