Integrations and data imports
Synchronize ERP customers
Synchronizes one ERPNext Customer into a HubSpot company.
Make it your own
Review the setup and limits below, then open an editable copy in Turbyn.
Use this recipeYour selection stays with you through signup.
What it does
Uses ERP Customer name as stable external ID; ambiguous matches fail.
What to customize
Configure the ERPNext HTTPS origin (without /api/resource) and bind both ERP credentials.
Run the included tests with your configuration and mappings. Review success, missing-input and failure results before publishing.
Expected outcome
This included example runs in dry-run mode with synthetic data. Integration tests separately cover provider responses using test doubles. It is not a live customer result.
Sample input
sample-input.json
{
"inputFields": {
"field1": "{\"customerId\":\"ERP-42\"}"
}
}Sample output
sample-output.json
{
"outputFields": {
"output1": "dry_run",
"output2": "",
"output3": "ERP-42"
}
}Returned fields
- output1
- status
- output2
- HubSpot company ID
- output3
- details
What changes when it runs
Reads ERPNext and creates or patches HubSpot companies.
Ready to try it with your rules?
Map your inputs, test a sample and publish the version you’ve checked.