Typically, the third-party application will send a payload to Integrator which will trigger an event-driven flow.
Read about user-defined APIs.
To test a flow without leaving Integrator, you will need to create another flow as a sender.
Let's assume that you have an example payload somewhere in a file-based or cloud storage. Let's also assume that you have already created and scheduled an event-driven flow and created an API user.
Step 2. Create a destination connection which sends a payload to the listener that you previously created for the event-driven flow.
For example, let's assume that:
- You are running Integrator on
- HTTP listener is used in the event-driven flow.
- The URL Pattern for the listener is configured as
If all of the above is true, create a destination HTTP connection for the sender flow with the following parameters:
- URL -
- Authentication -
- Authentication URL -
- HTTP Method for token Authentication -
- Access token attribute -
- Access token prefix -
- Authentication Request Payload -
- Authentication Request Content Type -
- User - user id for the API user
- Password - password for the API user
- Method -
Step 3. Create a transformation where the source (FROM) is the source connection and format you previously created in step 1, the destination connection is the connection you previously created in step 2, and the destination format = the previous source format.