CFT (Trigger)
The CFT Trigger Node enables your workflow to receive files securely transferred through Cloud File Transfer (CFT) platform. When a file is ready for download in CFT, the configured webhook triggers your workflow and provides the file content in base64-encoded format to start your workflow. For an overview of all input types, see Configure Workflow Input.
CFT Support: For any enquiries or issues related to CFT, please reach out to the CFT Service Desk via go.gov.sg/cft-sm.
How Does It Work?
The CFT Trigger Node acts as a webhook endpoint that receives file transfer notifications from the CFT platform. When a file is ready for download, CFT sends a webhook POST request that triggers your workflow with the file data.
Prerequisites: Configure applications and webhook in CFT system before setting up the Input Node. See How to Configure in CFT for detailed configuration steps. You need CFT credentials (Webhook Secret) as receiver from the Cloud File Transfer platform.
Setup Steps:
- Click on Select Input
- Choose CFT as the trigger node
- Choose the environment (Staging or Production)
- Open the trigger node Settings to configure the CFT connection
- Configure the following data:
- Webhook Secret: Secret key provided by CFT for webhook authentication
- Copy the webhook endpoint URL provided by the trigger node
- In the CFT platform, configure the webhook to point to the OPUS webhook endpoint URL
- Publish your workflow in OPUS to activate the webhook connection
- When a file is ready for download in CFT, it will send a webhook POST request to trigger the workflow automatically
Output:
The CFT Trigger Node returns the file content in the following format:
- data: Base64-encoded file content
- fileId: Unique identifier for the file
- traceId: Trace ID for tracking the request
Important: CFT will always return the output fields named as data, fileId and traceId.
This data becomes available to subsequent nodes, allowing the workflow to process file transfers automatically (e.g., decoding file content, parsing data, validation, transformation, database updates).
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:
mainbranch 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.
| Environment | Endpoint URL |
|---|---|
| Staging | https://lite.staging.oes.opus.gov.sg/api/cft/<namespace-id>/<project-id>/<entity-id>?branch=main |
| Production | https://lite.production.oes.opus.gov.sg/api/cft/<namespace-id>/<project-id>/<entity-id>?branch=main |
Query Parameters:
| Parameter | Description |
|---|---|
branch |
The branch or release version (e.g., main, release/1.0.0) |
identifier |
Optional. Custom identifier that appears in the monitoring page for easier tracking |
Example:
https://lite.staging.oes.opus.gov.sg/api/cft/namespace01/project01/cmj889fap00ysa401rpsjr98f?branch=mainWhen to Use It?
Use CFT Trigger Node when:
- You need to receive secure files from another agency through CFT.
- You are working with large file-based data transfers (e.g., CSV, Excel, XML).
- You want to automate the file-handling process when files arrive.
- You need real-time processing of file transfers from external government agencies.
- You want to trigger workflows based on file availability events in CFT.
Support
For any issues, please reach out to CFT Service Desk: go.gov.sg/cft-sm for support.
