🧪 Preview Feature!Â
This feature is in "Preview" and is limited to only users who opt-in for Preview use with Experience Cloud Version 6.10 & above.
 Are you interested in signing up and using the "Preview" feature? Please contact us here and let us know you're interested.
Â
Â
Â
Overview
The feature of PopFlow secures API connections within the OpenMethods Experience Cloud (Server-Side). Users can create their own connections which can be used repeatedly throughout the Experience Designer and PopFlow.Â
Â
The feature secures data using a patent-pending server-side authentication, helping protect data between applications in the browser and CRM.
Â
How to use App Connector
- From the Application Manager, you can click on 'App Connect".
- This will take you to the App Connect Management Screen.
- To add a new record, click on the 'Add New' button and fill out the form. (See Example Below)

Â
New Connector Fields
Form Option | Description |
---|---|
Connector Name | A name for the record. |
Auth Type | Two authentication types are available, Basic or Token. |
Domain | The Rest API root resource URL. |
Additional Headers | Additional headers to send with the HTTP request. |
Auth Prefix | The authorization header prefix when using a Token type of authorization. Common prefixes are Bearer or Session. Check with the connecting application's documentation to see what is accepted in your particular case. |
Auth Prefix Value | The value to be sent with the prefix. Example Bearer <token value>. |
Â
You can now use it in the Server Activity when designing your PopFlow Workflow.Â
- These App Connect records can be revoked at any time by selecting the "Trash" icon next to the record.
Â
Once you have created an application connection, use the following to call your connection securely within PopFlow's Experience Designer:
Â
Server-Side HTTPS/Webhook
🧪 Preview Feature! his feature is in ...
Server-Side HTTPS/Webhook

- When the PopFlow Script executes the Server Activity, the client will make a request to to the PopFlow Server Worker.Â
- The client will use the parameters defined the Server Activity in PopFlow Studio.
- The PopFlow Server Worker will then use the selected credentials in the Server Activity and securely use those credentials to complete the request.
Â
Build An AppConnector First
Before you can properly use the Server Activity, a App Connect (link) record needs to be created.
Â
Â
How the Server-Side Activity
Â
First, add the Server Activity.
Â
Â
Â
Then configure activity options:
Â
Â
Â
Server Activity FieldsÂ
Option | Description |
---|---|
Select Connected App | The list of available Connected Apps |
Method | The HTTP method to be used. |
Path | The path of the HTTP resource. |
Additional Headers | Additional headers to send with the HTTP request. |
Body | The HTTP body to send with the request. |
Timeout | The amount of time to wait for the request before timing out. |
Wait for result |
If true, it will wait for the request to return the results. If false, it will send the request and continue PopFlow execution immediately. |
Â
Â
Â