--- alias: user-guide-automation-task-core-sendnotificationtodriver tags: - automation tasks description: "Sends a direct message to a driver for real-time protocol customization" --- # Send Notification to Driver ![Screenshot showing a notification setup interface for sending a message to a driver.](../images/drivernotification-lg.svg) This task allows sending direct messages to the driver. It is used to allow real-time customization (when available) to the protocol process. ![Screenshot showing a notification type input field.](../images/image93.png) ## Inputs | Name | Data Type | Description | | -------- | --------- | ----------- | | type | `String` | Type of driver notification. | | Content | `String` | Content of the driver notification. | | Activate | `any` | Activate the notification send. | ## Outputs | Name | Data Type | Description | | ------ | -------- | --------- | | Success | `Boolean` | If there was no problem emits a `true` | | Error | `Error` | Error that occurred during the processing of this task | ## Settings On the *General Tab*, you have the usual settings and the following settings: | Name | Data Type | Default | Description | | ------ | -------- | --------- | --------- | | Type | `String` | | Type of notification to send. The expected value is different for each protocol (when supported) | | Content | `String` | | Content of the notification to send | ![Screenshot showing settings options, including a section labeled "Notification to Driver Settings".](../images/image94.png) ## Behavior In this task you choose a driver when dropping it into the workflow (if you have more than one driver associated with the controller). On `activate`, the task will send a notification to the pre-selected driver with a type and the contents converted to an object. ## Remarks Not all protocol drivers support/expect notifications. Each protocol driver has it's own set of expected types and content formats. Refer to their specific documentation for more information.