When building custom integrations, you can now see the requests you're sending and the responses returned from app servers, directly from the export 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.
|
Connector |
Field name |
Data displayed |
|---|---|---|
|
Common |
|
No |
|
MongoDB |
|
|
|
DynamoDB |
|
|
|
RDBMS (except bulk insert with Snowflake) |
|
|
|
Snowflake bulk insert |
|
|
|
HTTP |
|
|
|
REST |
|
|
|
AS2 |
|
|
|
FTP |
|
|
|
S3 |
|
|
|
Google Drive |
|
|
|
Azure |
|
|
|
Data loader |
||
|
Common |
|
|
|
NetSuite |
||
|
Salesforce |
Click Send 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 Fetch limit field.
The Preview pane displays the request URL, the HTTP request, the HTTP response, and the Parsed output.
Note
The sample record used in the Preview pane may not reflect a record within the time period you have set up for a delta export. Run a test flow to verify that delta exports are sending the intended records as expected.
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.
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.
Parsed output: This is the exported data record that was retrieved from the application source.
You can view the trace key associated with each record in the run details. Trace key helps correlate records across executions for troubleshooting and error tracking. If a trace key is not displayed for a record, the system was unable to detect or generate one. In this case, you can configure a custom trace key to improve tracking and auto-resolution behavior.
View records in JSON or tree format: You can view and inspect records in the JSON or Tree view format. This flexibility helps to analyze complex payloads, navigate hierarchical structures, and quickly identify the data elements that matter to you.
Important
JSON is the default view. View preferences are not saved across sessions or pages.
View single or multiple records: In the Parsed output tab, you can switch to view all records or a single record. This helps you check multiple records or focus on one record when you need more detail. You can copy all records in All records view or just the current record in Single record view.
Errors:
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.
You can now manually run a flow for a specific time range, allowing you to process records in controlled batches instead of running only up to the current time.
When you trigger a manual run, you can choose:
-
Automatic – Select a start date and time. Click Run, the flow runs up to the current time.
-
Custom – Select a start date, start time, and time zone, with an optional end date and time, then click Run.
During execution:
-
The start date time is passed to the export as last export date time.
-
The end date time (if provided) is passed as current export date time.
This enables batch processing for a defined period. To apply the end date and time, your export must reference current export date time. Some adapters, such as MongoDB, handle this automatically without additional configuration.
For delta exports on preview, if no new data is available from the current delta export date setting, the Delta preview dialog prompts you to select an earlier time and date.
You can now resize the configuration panel to focus on the section you’re working on and view more data. A drag handle is available between the configuration panel and the canvas area, with a default 50:50 split.You can hold and drag the handle to adjust the panel width. The panel resizes within defined minimum and maximum limits to ensure usability across different screen sizes. The layout remains responsive, the form fields adjust as you resize, and no horizontal scrolling is introduced.
Important: Your preferred width is saved at the account level and applies across all the flow steps.
You will see an indicator in the Mock section when the mock data doesn’t match the latest preview. The comparison runs after you click Send and only if mock data already exists.
Navigate to step → Export → Edit export page → Mock output.
Differences may include changed values, additional or removed fields, updated structures, or mismatched record counts for the following reasons:
-
You manually edit mock data and then click Send
-
Your mock data was generated earlier, and today’s preview returns different values
-
The endpoint returns new records or updated values
-
Field names, structures, or object shapes changed
-
The saved search or flow step configuration was updated without refreshing mock data
-
The number of records in mock data and preview differs
Important
The indicator appears only when the Send call is successful and the parsed output is updated.