Send message task and Receive message task nodes are used to handle the interaction between a running process and external systems. This is done using Kafka.
This node is used to configure messages that should be sent to external systems.
Node configuration is done by accessing the Node Config tab. You have the following configuration options for a send message task:
Inside the General Config tab, you have the following properties:
When encountering a step with canGoBack
switched to false, all steps found behind it will become unavailable.
To configure a send message task, we first need to add a new node and then configure an action (Kafka Send Action type):
Multiple options are available for this type of action and can be configured via the FLOWX.AI Designer. To configure and add an action to a node, use the Actions tab at the node level, which has the following configuration options:
PT30S
)You can configure Data to Send option only when the action trigger type is Manual.
For more information about Kafka, check the following sections:
Send a message to a CRM integration to request a search in the local database:
sendRequestToSearchClient
Parameters can be added either using the Custom option (where you configure everything on the spot) or by using From Integration and import parameters already defined in an integration.
More details about Integrations Management you can find here.
ai.flowx.in.crm.search.v1
the Kafka topic on which the CRM listens for requests{ "clientType": "${application.client.clientType}", "personalNumber": "${personalNumber.client.personalNumber}" }
- the message payload will have two keys, clientType
and personalNumber
, both with values from the process instance{"processInstanceId": ${processInstanceId}}
This type of node is used when we need to wait for a reply from an external system.
The reply from the external system will be saved in the process instance values, on a specified key. If the message needs to be processed at a later time, a timeout can be set using the ISO 8601 format.
For example, let’s think about a CRM microservice that waits to receive requests to look for a user in a database. It will send back the response when a topic is configured to listen for the response.
The values you need to configure for this node are the following:
ai.flowx.out.crm.search.v1
A naming pattern must be defined on the process engine to use the defined topics. It is important to know that all the events that start with a configured pattern will be consumed by the Engine. For example, KAFKA_TOPIC_PATTERN
is the topic name pattern that the Engine listens to for incoming Kafka events.
crmResponse
For more information about Kafka configuration, click here.
After defining one integration (inside Integration Management), you can open a compatible node and start using already defined integrations.
processInstanceId
as a default header parameter; add any other relevant parametersSend message task and Receive message task nodes are used to handle the interaction between a running process and external systems. This is done using Kafka.
This node is used to configure messages that should be sent to external systems.
Node configuration is done by accessing the Node Config tab. You have the following configuration options for a send message task:
Inside the General Config tab, you have the following properties:
When encountering a step with canGoBack
switched to false, all steps found behind it will become unavailable.
To configure a send message task, we first need to add a new node and then configure an action (Kafka Send Action type):
Multiple options are available for this type of action and can be configured via the FLOWX.AI Designer. To configure and add an action to a node, use the Actions tab at the node level, which has the following configuration options:
PT30S
)You can configure Data to Send option only when the action trigger type is Manual.
For more information about Kafka, check the following sections:
Send a message to a CRM integration to request a search in the local database:
sendRequestToSearchClient
Parameters can be added either using the Custom option (where you configure everything on the spot) or by using From Integration and import parameters already defined in an integration.
More details about Integrations Management you can find here.
ai.flowx.in.crm.search.v1
the Kafka topic on which the CRM listens for requests{ "clientType": "${application.client.clientType}", "personalNumber": "${personalNumber.client.personalNumber}" }
- the message payload will have two keys, clientType
and personalNumber
, both with values from the process instance{"processInstanceId": ${processInstanceId}}
This type of node is used when we need to wait for a reply from an external system.
The reply from the external system will be saved in the process instance values, on a specified key. If the message needs to be processed at a later time, a timeout can be set using the ISO 8601 format.
For example, let’s think about a CRM microservice that waits to receive requests to look for a user in a database. It will send back the response when a topic is configured to listen for the response.
The values you need to configure for this node are the following:
ai.flowx.out.crm.search.v1
A naming pattern must be defined on the process engine to use the defined topics. It is important to know that all the events that start with a configured pattern will be consumed by the Engine. For example, KAFKA_TOPIC_PATTERN
is the topic name pattern that the Engine listens to for incoming Kafka events.
crmResponse
For more information about Kafka configuration, click here.
After defining one integration (inside Integration Management), you can open a compatible node and start using already defined integrations.
processInstanceId
as a default header parameter; add any other relevant parameters