A data push node delivers query results from upstream nodes in a DataWorks workflow to DingTalk, Lark, WeCom, Teams, or email, keeping your team informed of the latest data.
How it works
A data push node uses the Input and Output Parameters to retrieve output parameters from upstream SQL query nodes and assignment nodes. You can then use these parameters as placeholders in the message body and push them to a destination.
After an SQL query node runs, it generates an
outputsparameter that contains the query results and passes them to downstream nodes. For more information, see Configure node context.When you configure the message body in a data push node, you can use the
${Parameter name}format in a Markdown component to reference and display output parameters from an upstream node.To display data in a table component, select the field names from the upstream SQL query in the component's associated parameter setting.
Prerequisites
The DataWorks service is activated. For more information, see Purchase guide.
A DataWorks workspace is created. For more information, see Create a workspace.
A workflow is created in your DataWorks workspace.
A serverless resource group is required, as this node can run only on a serverless resource group. To purchase and use a serverless resource group, see Use serverless resource groups.
Public network access is enabled for the resource group. For more information, see Overview of network connectivity solutions.
Limitations
The following data size limits apply when pushing data to different destinations:
DingTalk: The message size cannot exceed 20 KB.
Lark: The message size cannot exceed 20 KB, and images must be smaller than 10 MB.
WeCom: Each chatbot cannot send more than 20 messages per minute.
Teams: The message size cannot exceed 28 KB.
Email: Each data push task supports only one email body. For other limitations, refer to the SMTP limits of your email service provider.
The data push node is available only in workspaces in the following regions: China (Hangzhou), China (Shanghai), China (Beijing), China (Shenzhen), China (Chengdu), China (Hong Kong), Singapore, Malaysia (Kuala Lumpur), US (Silicon Valley), US (Virginia), and Germany (Frankfurt).
1. Create an upstream node
A data push node retrieves Context Parameters from an upstream node's context to push them to a destination. Before you create a data push node, create an upstream SQL query node or assignment node.
To push data from MaxCompute, you must use an assignment node to query the data and generate output parameters in the Properties panel. For more information, see Push MaxCompute data.
If the upstream node queries a different data source, it generates an
outputsoutput parameter. This parameter is then passed to the data push node. For more information, see Best practices: Configure a data push node in a workflow.
SQL query node
Log on to the DataWorks console. In the target region, click in the left-side navigation pane. Select a workspace from the drop-down list and click Go to Data Development.
Double-click your workflow to open the canvas. Click
to create an SQL query node.Double-click the SQL query node to open its editor and write your query.
NoteA data push node cannot directly fetch data from an ODPS SQL query. You must use an assignment node and configure the query within it. For more information, see Configure a push workflow.
In the right-side pane, click Scheduling to configure the node's scheduling settings.
For detailed steps to Configure Scheduling Settings, see Configure Basic Properties, Time Property Configuration, Configure Resource Properties, Configure Same-Cycle Scheduling Dependencies, and Configure Node Context.
On the Scheduling panel, navigate to and click Add assignment parameter to expose the SQL query results as an output parameter.
Click the
Save icon.
Assignment node
Log on to the DataWorks console. In the target region, click in the left-side navigation pane. Select a workspace from the drop-down list and click Go to Data Development.
Double-click your workflow to open the canvas. Click
to create an assignment node.Double-click the assignment node to open its editor.
An assignment node uses ODPS SQL, Shell, or Python for value assignment. For more information, see Assignment node.
After you configure the node, click the
Save icon.
2. Create a data push node
On the workflow canvas, click
to create a data push node.Parameter
Description
Node Type
Select Data Push from the drop-down list.
Path
Select the path that contains the upstream node from Step 1.
Name
Enter a name for the node.
Double-click the new data push node to open its configuration page.
In the right-side pane, click Properties. Under , click Add to set the node you created in Step 1 as an upstream dependency.
On the Properties panel, under , select a serverless resource group created on or after June 28, 2024. If your resource group was created before this date, you must submit a ticket to upgrade it.
On the Properties panel, under , click Add to create an input parameter. For its value, select the output parameter of the query node from Step 1. Then, close the Scheduling panel.
On the node's configuration page, configure the destination, title, and body of the message.
From the Destination drop-down list, select a destination. If your desired destination is not listed, click Create Data Push Destination to create it.
Parameter
Description
Type
Supported types: DingTalk, Lark, WeCom, Teams, and Email.
Object
The name for the destination.
Webhook
The webhook URL for a DingTalk, Lark, or WeCom chatbot; the incoming webhook for Teams; or the SMTP details for email. Obtain this information from the target platform.
NoteFor how to obtain a Lark bot Webhook, see Configure a Lark Webhook trigger.
For how to obtain a Teams Webhook, see Use Microsoft Teams workflows to create an incoming Webhook.
To manage push destinations:
Log on to the DataWorks console. In the target region, click in the left-side navigation pane. Select a workspace from the drop-down list and click Go to DataService Studio.
On the Service Development page, click the
Settings icon in the lower-left corner and go to the Destination Management tab. On this tab, you can manage existing destinations or click Create Data Push Destination to add a new one. For more information, see Create a webhook data push destination.
Name: Enter a title for the message.
Body: You can add Markdown and Table components. For more information, see Configure push content.
NoteIf the upstream node is an SQL query node:
In the Markdown body of a data push, use field names from an SQL query as placeholders in the
${field_name}format to retrieve upstream output parameters.For tables in a data push body, use field names from an upstream SQL query as Parameters to retrieve data.
If the upstream node is an assignment node, you must use a placeholder in the format
${Input parameter name}in the message body. ${Input parameter name} is the name of the Input Parameters you configured on the data push node.
Click the
Save icon to save the data push node.
3. Run and deploy the task
After you configure the data push workflow, test it to verify that it runs correctly, then commit and deploy the task.
On the workflow canvas, click the
Run icon to run the workflow.After the
success icon appears on all nodes, click the 
Commit icon to commit the workflow.In the Submission dialog box, select the nodes you want to commit and select the Ignore I/O Inconsistency Alerts checkbox.
Click Submission.
After the nodes are successfully committed, deploy them. For more information, see Publish tasks.
Best practices
The data push node supports several workflow patterns: simple push, combined push, script-based push, conditional push, and MaxCompute push. For more information, see Best practices: Configure a data push node in a workflow.
Next steps
After deployment, manage the task in Operation Center. For more information, see Perform basic O&M operations on auto triggered nodes.