Import node

Purpose

• Pull data from ERPs, bank APIs, payment processors, email attachments, cloud, and file-based sources
• Schedule imports to run automatically, without manual exports or downloads
• Support one-time and recurring imports across multiple sources in a single workflow run

Inputs

• ERPs and accounting software: Payroll data, account balances, and more
• Banks: Transactions, account statements, balances, and more
• Payment processors: Transactions, fee structures, contract terms, settlement statements, and more. See the growing list of providers we're connected with.
• Files: From manual uploads or cloud storage
• Databases: usage data, transactional data, or any other data stored there
• Email attachments: Vendor invoices, purchase orders
• Other vendor portals: Invoices from the billing section of any SaaS tool

Outputs

• Structured data ready for the next actions
• Import logs with source, timestamp, and status

Typical use cases

All workflows start with some sort of a data import node to get the data into the workflow.

• The payment reconciliation workflow imports data from past workflows, PSP back offices, and internal databases.
• The purchase order and invoice matching workflow pulls purchase orders from the ERP, invoices from emails, and unmatched items from previous Reiterate workflows.