Patch Conversation Object Name and Email
Updates the requester name and email of a DigitalGenius conversation. Use it in Chat flows without a pre-chat form, or in Voice flows, to set customer details found during the flow.
What it does
- Updates the requester name, email, or both on the conversation identified by the root flow ID and conversation ID.
- Sends only the fields you provide, so an empty Name or Email keeps its current value.
- Authenticates with your DigitalGenius connection, so you don't need a DG API Key and Secret.
- Returns whether the requester was updated.
Use this action when the customer's details aren't available at the start of a conversation. For example, use it in Chat flows that have no pre-chat form. You can also use it in Voice flows that get the name and email from order data.
Inputs
| Name | Type | Description |
|---|---|---|
| Root Flow ID | String | The root flow ID. For Email and Chat flows, this is the ID of the Entry Flow. For Voice flows, this is the ID of the Call Start Flow. |
| Conversation ID | String | The conversation ID. |
| Name | Optional String | The requester's name. Leave empty to keep the current name. Name or Email is required. |
| Optional String | The requester's email address. Leave empty to keep the current email. Name or Email is required. | |
| Safe Mode | Optional Boolean | When true, the action returns Success as false with an error message instead of raising an error. Defaults to false. |
Outputs
| Name | Type | Description |
|---|---|---|
| Success | Boolean | Whether the requester was updated. False when Safe Mode is on and the update failed. |
| Error Message | String | Why the requester wasn't updated. For example, the connection is missing or Name and Email are both empty. Empty on success. |
Notes
- The action needs a DigitalGenius connection. The region comes from the connection, so the action has no Region input.
- Provide at least one of Name or Email. If both are empty, the action fails.
- If the request fails, the action raises an error. Turn on Safe Mode to handle the failure in the flow with the Success and Error Message outputs instead.
- This action replaces the HTTP Request action with DG API Key and Secret for updating the conversation requester.
Updated 3 days ago
Did this page help you?
