Once a file is transformed and submitted, the output still has to reach its destination. Exporters define where WeTransform delivers the transformed data: your API, your inbox, a file server, or your application. They are configured per target format, and every submission triggers them automatically, no manual download needed.
📦 The five exporters
☁️ API push — sends your transformed data to your API endpoint as JSON, one HTTP request per row. Ideal to feed an ERP, PIM, or CRM record by record, with no import step. See Exporter: API push.
⚡ Webhook — notifies your application the second a file is ready, with a signed download link. Your system downloads the file and takes it from there. See How to receive your output automatically with webhooks.
📧 Email — sends the transformed file by email to your team, as an attachment. See Exporter: Email.
🗂️ FTP — uploads the transformed file to an FTP server. See Exporter: FTP and SFTP.
🛡️ SFTP — uploads the transformed file to an SFTP server, over an encrypted connection.
⚙️ How to add an exporter
Open the Target formats page and click Exporters on your target format
Click Add a new exporter
Choose the destination for your transformed data
Fill in the connection details (endpoint URL, email address, or server credentials)
💡 You can combine several exporters on the same target format. Each submission triggers all active exporters, so the same output can be pushed to your API and mailed to your team at the same time.
🧭 API push or webhook?
The two look similar but do different things:
API push delivers the data itself. WeTransform sends one JSON request per row to your endpoint. Your system receives records, not a file.
Webhook delivers a notification. WeTransform tells your application the file is ready and hands it a download link. Your system fetches the whole file.
Choose API push to feed a system record by record. Choose the webhook when your system prefers to process the complete file.
🏭 Example — a supplier catalog, delivered twice
A retailer receives a weekly price list from a supplier. On the target format, two exporters are active:
API push sends each product row as JSON to the retailer's PIM
Email sends the full transformed file to the purchasing team
Every Monday the supplier's file arrives, is transformed, lands in the PIM, and reaches the team's inbox, with nobody touching anything.
👉 What to do next