When building custom integrations, you can now see the requests you're sending and the responses returned from app servers, directly from the configuration screens of your source apps. This helps you see how your request is constructed in integrator.io, and preview the communication with the app server before committing to running the full flow.
Exports are used to extract data from an application or system. Exports running in the context of a Flow will execute asynchronously and automatically break exported data down into one or more pages and then stream those pages to one or more Imports.
You can use the Preview pane to verify the following:
- You have configured your request correctly.
- Data is successfully retrieved.
Note: If data is not successfully retrieved, the Preview pane displays the error message returned by the application you are connecting with to help you troubleshoot the configuration.
Click Preview on the Edit export window to send the configured request to the server. If successful, sample records display in the Preview pane. If not, the error response displays instead. You can specify the number of records you would like to review in the preview panel by entering a number up to 100 in the Number of records field.
The Preview data section displays the request URL, the HTTP request, the HTTP response, and the Parsed output.
HTTP request: This is the request that integrator.io sends to the application you are connecting with. In the following image, the request has no body because it was a simple GET request. You can click Headers to review the information included in the call's header, and Other to see the structure of the GET call sent.
HTTP response: This is the response body returned by the application server. You can also review the headers or any information returned by the response by clicking Headers or Other.
Output: This is the exported data record that was retrieved from the application source.
If the application detects one or more errors, the Preview pane displays the number of errors detected. The error screenshot below is an example of what the Preview pane displays if the HTTP request is not correctly configured. If an error with the export occurs (meaning that the request is correct but what is returned is not), then the error displays in the HTTP response.