FormSG (Trigger)

The FormSG Node enables your workflow to receive secure form submissions from FormSG, Singapore’s trusted form builder for government agencies. When a citizen or staff member submits a form, the configured webhook triggers your workflow and provides the form data to start automated processing.

Note: FormSG is a secure form building platform for government agencies. For an overview of all trigger nodes, see Configure Workflow Input.

FormSG Support: For any enquiries or issues related to FormSG, please reach out to the FormSG team via go.gov.sg/formsg-support.

How Does It Work?

The FormSG Node acts as a trigger that receives webhook POST requests whenever a form is submitted. It authenticates incoming webhooks using a secret key to ensure data integrity and security.

Prerequisites: You need a FormSG Secret Key from your FormSG form configuration to verify webhook authenticity. This key is used to validate that incoming requests are genuinely from FormSG.

Setup Steps:

1. Click on Select Input
2. Choose FormSG as the trigger node
3. Open the trigger node Settings to configure the FormSG connection
4. Enter the FormSG form link to connect to your form
5. Check the connection to ensure it is a valid FormSG form link
6. Provide the FormSG Secret Key to verify webhook authenticity and ensure secure data transmission
7. Copy the webhook endpoint URL provided by the trigger node
8. Navigate to FormSG and go to Settings > Webhook
9. Paste the webhook endpoint URL in FormSG
10. Publish your workflow in OPUS to activate the webhook connection
11. Each form submission will now send a webhook POST request to trigger the workflow automatically

Runtime URL

The trigger node provides runtime URLs for invoking your workflow in different environments:

• Staging URL: Used for testing in the staging environment
• Production URL: Used for live production workflows

The URL format indicates the specific branch or release version:

• main branch for development
• Release versions (e.g., release/1.0.0) for production deployments

Note: The endpoints below are for Lite tier reference only. Always refer to the endpoint URL shown in your node settings.

Query Parameters:

Example:

https://lite.staging.oes.opus.gov.sg/api/formsg/namespace01/project01/cmj889fap00ysa401rpsjr98f?branch=mainCopy to clipboardErrorCopied

Output

When a form is submitted, the FormSG Trigger node outputs the decrypted form field responses along with a _meta object containing submission metadata.

Output Structure:

{
  "_meta": {
    "formId": "67d27ca5d1e48166ca6faeb7",
    "submissionId": "682ef8213ea3ba1b2c109a8e",
    "created": "2026-03-08T10:10:41.253Z"
  },
  "What is your name?": "John Doe",
  "What is your email?": "john@example.com"
}Copy to clipboardErrorCopied

Metadata Fields:

The form field responses are included alongside _meta at the root level, keyed by their field labels. These can be accessed by downstream nodes using template expressions (e.g., {{{ data._meta.submissionId }}}).

When to Use It?

Use FormSG Node when:

• You need to automate processing of government form submissions.
• You are collecting data through FormSG and want to trigger automated workflows.
• You want to integrate form submissions with backend systems, databases, or APIs.
• You need real-time processing of form data (e.g., sending notifications, creating records, triggering approvals).
• You want to reduce manual data entry and processing time.

Tip: Combine with Decision Nodes or Expression Nodes to validate and route form submissions based on specific criteria. Use Function Nodes or API Nodes to integrate with external systems for data storage or further processing.