Triggered by HTTP

Introduction

Feature Overview

Automations Pro can be triggered when it receives third-party data via a URL (generated and provided by Automations Pro), and execute the preset workflows automatically.

Scenarios

Automations Pro Triggered by HTTP is often used for real-time updates that require external information be written back to Jodoo forms, creating a closed-loop business process.

Scenario Name	Problem Statement	Solution on Jodoo
Logistics Status Updates	How to write back real-time logistics status updates created by the third party to Jodoo forms?	Set an automation that generates a URL, to which the third-party system sends an HTTP request, and from which Jodoo receives it and updates the related form.
Invoice Status Updates	When an invoice is issued, how to immediately update its status in Jodoo forms?
Contract Status Updates	When an electronic contract is signed on an online platform, how to update its status in Jodoo forms?

Implementation Mechanism

Automations Pro Triggered by HTTP provides a subscription mechanism for external systems. When an event occurs in an external system, it sends data with an HTTP request via a specified URL to Jodoo, which triggers Automations Pro to perform the corresponding action.

1. Automations Pro provides a URL to receive HTTP requests.

2. The URL is configured in the external system to send requests upon events.

3. Automations Pro receives and processes the event data to execute business processes.

Instructions

Automations Pro's request handling frequency varies by configuration:

Enabled with IP whitelist: 20 requests per second
Enabled without IP whitelist: 1 request per second
Disabled: 1 request per second

Setup Steps

Selecting a Trigger Type

Go to App Management > Automations, click New Automation, and select Triggered by HTTP.

Click OK to proceed to the design page.

Configuring Trigger Address

Trigger Address is a specific URL provided by Automations Pro for receiving HTTP requests from external systems. Copy this URL, and configure it in the external system.

Note:

1. Each new HTTP-triggered Automations Pro gets a unique, fixed URL.

2. Duplicated automations receive a new URL.

Trigger Configuration (Optional)

1. Specify allowed IPs

Enable the IP whitelist to ensure only trusted sources can trigger Automations Pro:

Check Set IP Whitelist to enable the whitelist.
Click Add IP and enter the allowed IP addresses.
Click OK to save the settings.

Note:

Without a whitelist, all IPs can trigger the automation.
Only IPv4 addresses and an IP address range with a wildcard (*) are supported.
Up to 50 IP addresses can be added.

2. Customize the response

Automations Pro returns a response to the push address upon receiving a request. You can customize this response:

Check Set Custom Response, and click Set Response.
Choose the format and enter the response content.

Trigger Data List

Trigger Data List shows the parameters parsed from received requests, which will be used in subsequent workflows (i.e. be referenced by following action nodes).

Click Click to Retrieve Sample Data and push sample data to Trigger Address within 3 minutes. In this way, you can view the trigger data list.

Note:

1. After clicking Click to Retrieve Sample Data, data is captured within a 3-minute window before and after the click.

2. Text, Number, and text array fields are supported, with specific parsing rules.

Received dates are converted to text format. You can use formulas to convert them back to date format if it is needed in subsequent processes.
Numbers with more than 8 decimal places are rounded to 8 decimal places.
Numbers and dates within arrays are converted to text format.

3. Null, empty strings, and empty JSON are treated as empty values.

Error Codes

Automations Pro returns specific error codes and messages when a trigger fails:

Error Code	Error Message	Description
8304	The call frequency exceeds the frequency limit.	Request exceeds frequency limit.
100003	Automated global configuration does not exist.	Automations Pro has been deleted.
100105	The trigger is not enabled.	Automations Pro is not enabled.
———	Request entity too large.	Request body exceeds the 2M limit.

Notes

1. The parsed data is stored in the trigger node for subsequent use, but cannot be updated or deleted. That is, at a subsequent Update Record/Delete Record, if you choose to update/delete Record at the node, you cannot select the trigger node.

2. If a whitelist is configured, only IPs in the whitelist of the published version can trigger the automation.

3. In Trigger History, you can click View Details > the Triggered by HTTP node, to view Trigger IP and Triggered Data .