📄️ Nodes Overview
Nodes are the building blocks of any workflow in Hashdata. Each node represents a step in the process — whether it is the event that starts the automation, an action that sends an email, a conditional decision, or a wait for approval. By connecting nodes in sequence, you visually describe the entire workflow without writing a single line of code.
📄️ Trigger: Form Response
The Trigger: Form Response node automatically starts a workflow whenever a Hashdata form receives a specific action — such as the submission of a new response, the modification of an existing response, or the deletion of a response. It is the most common starting point in data collection-oriented workflows, as it directly connects the filling of a form to the start of an automated process.
📄️ Trigger: Scheduled
The Trigger: Scheduled node starts a workflow automatically at regular time intervals, without depending on any human interaction. Unlike the form-based trigger, this node is fired by the system itself according to the configured frequency — daily, weekly, bi-weekly, or monthly — enabling reliable and predictable automation of recurring tasks.
📄️ Node: Approval
The Approval node interrupts the workflow execution and sends a decision request to one or more approvers. The process only advances — or follows the timeout path — after someone clicks one of the configured decision buttons. It is the ideal node for any step that requires human review before continuing.
📄️ Node: Send Email
The Send Email node allows your workflow to send personalized email messages to any recipient at the exact moment the step is reached. It is ideal for automatic notifications, receipt confirmations, internal communications, and any situation where a person needs to be informed about the progress of a process.
📄️ Node: Request Form Response
The Request Form Response node invites one or more recipients to respond to a Hashdata form. Unlike a simple email send, this node pauses the workflow execution until the response is received — or until a timeout deadline is reached, if you have configured one. Only after the response (or the deadline expiration) does the flow advance to the next node.
📄️ Node: Request Follow-Up
The Request Follow-Up node allows a workflow to ask one or more people to revisit and complement a form response that was previously submitted. Instead of creating a new blank record, the recipient receives an email invitation and, when clicking the link, opens exactly the original response — being able to edit the available fields, add missing information, or correct incorrect data.
📄️ Node: Set Status
The Set Status node allows you to configure a descriptive text for the workflow instance. This text is displayed in the Last step column in the instance panel, allowing any team member to quickly identify what stage each instance is in — without needing to open the detailed history.
📄️ Node: Join
The Join node is responsible for synchronizing parallel branches within a workflow. It waits for the convergence of all ongoing branches before allowing the flow to continue to the next step. Without it, branches running in parallel never meet again, and the rest of the process cannot proceed in a controlled manner.
📄️ Node: Wait
The Wait node pauses the workflow execution for a configurable period of time. When the defined time expires, the instance automatically advances to the next node, with no manual intervention required.
📄️ Node: If/Else
The If/Else node is the conditional decision node of the Hashdata Workflow. It analyzes the content of responses collected up to that point in the flow and directs execution to one of two possible paths: True or False. With this node, you create smart workflows that automatically adapt to the content of responses, without needing manual intervention for each case.
📄️ Node: Webhook Out
The Webhook Out node makes an HTTP call to an external URL during the workflow execution. With it, you can integrate Hashdata with any system that has a REST API — without needing a dedicated native connector. Whenever an instance passes through this node, Hashdata sends a request to the configured address and waits for the response before proceeding to the next step.
📄️ Node: Create PDF
The Create PDF node generates a custom PDF file during workflow execution. You define the content using a rich visual editor — with support for formatted text, tables, and workflow variables — and the resulting PDF becomes an artifact available to downstream nodes: it can be attached to emails, uploaded to Google Drive or OneDrive, and referenced at other points in the flow.
📄️ Node: Workflow History
The Workflow History node automatically generates a PDF with the complete event history of the running instance. Unlike the Create PDF node, which lets you compose a custom document, this node produces a structured report generated by the system itself — no content configuration needed. You only set the page format and orientation.