Integrations and data imports
Import campaign performance metrics
Import HubSpot campaign performance into a pre-created custom object keyed by reporting period.
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
At most 100 campaigns and explicit partial status.
What to customize
Set the pre-created custom object ID, unique period property, mapped metric properties, and campaign bound.
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": "{\"periodStart\":\"2025-01-01\",\"periodEnd\":\"2025-01-31\"}"
}
}Sample output
sample-output.json
{
"outputFields": {
"output1": "dry_run",
"output2": "",
"output3": "{\"period\":[\"2025-01-01\",\"2025-01-31\"]}"
}
}Returned fields
- output1
- imported, partial, failed
- output2
- count
- output3
- period and failures
What changes when it runs
Lists campaigns with cursor pagination, reads documented reports/metrics, and upserts the configured custom object.
Ready to try it with your rules?
Map your inputs, test a sample and publish the version you’ve checked.