If you receive files into an Amazon-style target format, chances are they come from a handful of known systems: Magento, Prestashop, Sage, Salesforce. Asking every customer to rebuild the same set of rules from Sage to your format is wasted work, theirs and yours.
A connector acts as a bridge that automates the transformation between a known source format and your target format. You define the transformation steps once; when a customer uploads a file in that format, WeTransform recognizes it and applies the steps automatically.
✨ What your customers experience
When a customer uploads a file, WeTransform compares its source columns with the connectors existing on your target format. If the columns match a connector, the customer is asked:
💬 "Is this file coming from Sage?"
If they click Yes, all the transformation steps from the connector are duplicated into their new transformation. Instead of starting from a blank mapping, they start from a working one.
⚠️ Quickfixes are not copied. One-off corrections applied to a specific file stay with that file. Only the reusable transformation steps carry over.
⚙️ How to create a connector
Create a transformation using a sample file in the right source format (for example a real Sage export), and configure the transformation steps as usual
Go to your transformations history
On the transformation, open the settings menu and click Make it a connector (⚡)
Give the connector a name your customers will recognize, for example Sage. You can also add a logo
🏭 Example — an HR platform receiving employee files
An HR platform defines a target format to receive employee information. Its customers export from Sage or Salesforce, each with its own file structure. The platform creates one transformation from a sample Sage export, promotes it to a Sage connector, and does the same for Salesforce. From then on, every customer uploading a Sage file is offered the ready-made transformation, and the platform never explains the same mapping twice.
👉 What to do next