Integrations and data imports

Import invoices into CRM

Imports Stripe invoice totals, status, currency and line snapshots into a configured HubSpot custom object.

Available recipeIncludes configuration, sample data and tests

Make it your own

Review the setup and limits below, then open an editable copy in Turbyn.

Use this recipe

Your selection stays with you through signup.

What it does

One invoice per invocation; strict line completeness and a CRM-verified unique invoice identity.

What to customize

Configure the existing custom object type ID and property mappings; create a unique text invoice identity property before running.

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": "{\"invoiceId\":\"in_123\"}"
  }
}

Sample output

sample-output.json

{
  "outputFields": {
    "output1": "dry_run",
    "output2": "",
    "output3": "Stripe read and CRM writes suppressed"
  }
}

Returned fields

output1: created, updated, failed
output2: HubSpot custom-object record ID
output3: reason

What changes when it runs

Reads Stripe invoice and creates or patches CRM invoice.

What you’ll need

JSON invoiceId

Stripe key with invoice read access.

HubSpot custom objects entitlement, object read/write and schema read access.

Pre-create a custom object with stripe_invoice_id (unique text), invoice_status (text), invoice_currency (text), invoice_amount_due (number), invoice_lines_json (multiline text), or map equivalent properties.

Setup

Create the custom object and listed properties; copy its 2-... object ID into configuration.
Bind STRIPE_SECRET_KEY and map invoiceId.
Run local tests, then verify a representative invoice in a test portal.

Secrets

STRIPE_SECRET_KEY

Limits

amount_due retains Stripe integer minor units; no currency scaling is inferred.
Lines are stored as a JSON snapshot, not separate CRM line-item records.
Invoices with a paginated/incomplete line list are rejected for explicit reconciliation.
No invoice is issued, payment taken or accounting record updated in Stripe.

Follow the setup guide

Ready to try it with your rules?

Map your inputs, test a sample and publish the version you’ve checked.

Use this recipe