Integrations and data imports

Match a contact against a customer database

Finds one customer row by primary key through Supabase PostgREST.

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

Primary-key lookup distinguishes no match and ambiguity.

What to customize

Set an HTTPS PostgREST URL and bind the read key.

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": "{\"rowId\":\"cust_123\"}"
  }
}

Sample output

sample-output.json

{
  "outputFields": {
    "output1": "dry_run",
    "output2": "",
    "output3": "cust_123"
  }
}

Returned fields

output1: status
output2: row ID
output3: customer details

What changes when it runs

Reads at most two rows; no CRM writes.

Ready to try it with your rules?

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

Use this recipe