What are exports?

In the context of a flow, an export is a flow step that retrieves data from an application. You can think of an export as the source application that supplies the initial data at the beginning of a flow. An export retrieves information from an application, and an import deposits data into an application.  A flow can have multiple export steps, but any complete flow must include at least one export, data loader, or webhook listener flow step.

If your flow contains multiple exports, the data retrieved from each export application is kept independent and seperate from any other export data that passes through the flow. This means that any export data retrieved from one export step passes through all subsequent flow steps before the flow begins processing data from another export flow step.

Start creating an export from a source application in either of the following ways:

• From the Tools menu, select Flow builder. Then, click Add source.
  – or –
• From the Resources menu, select Exports. Then, click + Create export.

An export must have a connection to the source application. Connections authenticate your access to an API, and integrator.io has branded connectors that are customized for many common platforms, but you can also use universal HTTP, REST, FTP, and AS2 connectors to create connections to any platform. If you use a branded connector to establish a connection for an export, the options available in the export settings menu are also customized to the known requirements of the platform. When using universal connectors, the export settings display all possible fields necessary to connect to any API, and some of those settings may not be relevant to the platform you are exporting data from.

Click the plus sign on an export flow step to configure additional options for your flow's behavior.

1. Click the calendar icon to override the integration flow schedule for this export. If this flow has been scheduled to run at specific intervals at the integration level, you can open the Flow schedule override page to use a different scheduling strategy for this export. See Flow schedules.
2. Transform your export data to accommodate future flow steps. See Transform your data records.
3. Filter the export data to include/exclude specific records. See Apply filters.
4. Create a pre save hook to perform complex logic on the export data. See Export hooks.

See the following articles for steps on creating exports with universal connectors:

• • Export data from an HTTP source app
  • Export files from an FTP server