Objective

Enable native support in Appsmith for API actions routed through Paragon Proxy, using predefined templates and dynamic parameters.

🛠️ How It Works

1. UQI Integration
   1. Add a new action type where the command starts with PROXY_.
   2. When selected, the UI will show predefined fields (inputs/children) from UQI.
2. Cloud Services Logic
   1. On action execution, Appsmith checks if the command starts with PROXY_.
   2. If true, it:
      1. Fetches the Action Template from the Cloud Services database.
      2. Builds the request using the template (path, body, headers, etc.).
      3. Sends the request to the Paragon Proxy API, including the Paragon Bearer Token.
3. Action Template Collection (Database)
   1. Stores the config for each proxy action (path, headers, body, query params).
   2. Automates runtime parameter mapping.

UQI Example (Create Zendesk Ticket)

https://jsonblob.com/1352244325299445760

Logic in CS

If the command starts with PROXY_, check the action template collection in cloud services.

Action Template Document in CS DB (Create Zendesk Ticket)

https://jsonblob.com/1352244743245062144