GovEntry (Trigger)

Beta Feature: This node is currently in beta. Features and functionality may be subject to changes.

The GovEntry Trigger Node enables your workflow to receive event notifications from GovEntry, Singapore Government’s access validation platform. When a registration event occurs, the configured webhook triggers your workflow to process the event.

Note: GovEntry is a platform for managing government access validation designed for registration and attendance tracking. For an overview of all trigger nodes, see Configure Workflow Input.

GovEntry Support: For any enquiries or issues related to GovEntry, please reach out to the GovEntry team.

How Does It Work?

The GovEntry Trigger Node acts as a webhook endpoint that receives POST requests whenever a registration-related event occurs in the GovEntry platform. It processes the incoming event data and makes it available to subsequent nodes in your workflow.

Prerequisites: GovEntry supports optional payload encryption for webhooks. You may opt in by generating a public and private key pair following these instructions, you must also provide the corresponding private key in the trigger node settings so that incoming requests can be decrypted. If you are not opting for payload encryption, the private key field must be left empty.

Setup Steps:

1. Click on Select Input
2. Choose GovEntry as the trigger node
3. Open the trigger node Settings
4. [Optional] If you are opting for payload encryption, provide the private key. Otherwise, leave this field empty.
5. Copy the webhook endpoint URL provided by the trigger node
6. Navigate to GovEntry and go to Webhook Details > Add Webhook(s) to configure the webhook to point to the OPUS webhook endpoint URL
7. Paste the webhook endpoint URL in GovEntry
8. [Optional] If opting for payload encryption, paste the public key in GovEntry
9. Click on Add
10. Publish your workflow in OPUS to activate the webhook connection

Output:

The GovEntry Trigger Node returns the event data in the format provided by the GovEntry platform.

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.production.oes.opus.gov.sg/api/GovEntry/namespace01/project01/cmisfd7yx000h8u01dpzdrbw4?branch=mainCopy to clipboardErrorCopied

When to Use It?

Use GovEntry Trigger Node when:

• You need to automate processing of registration events.
• You are managing registration and attendance through GovEntry and want to trigger automated workflows.
• You want to integrate registrations with backend systems, databases, or notifications.
• You need real-time processing of registration events (e.g., sending confirmations, creating or updating records, triggering fulfillment).
• You want to automate registration and attendance workflows.