Skip to content

Guides

How to build integrations and automations

Step by step guides with the Tray Headless prompts that build each one. Work in your coding assistant, governed by default.

Revenue operations

How to build lead import and validation

Validate before you write, quarantine the bad rows instead of dropping them, dedupe against what is already there, and keep the source.

Automation

SalesforceGoogle DriveMarketoSlack

How to build lead routing that assigns in seconds

Match the lead to an account first, evaluate rules in a fixed order, catch what they miss, and time it from arrival.

Automation

SalesforceMarketoClearbitSlack

How to build lead-to-account matching

Domain first, then fuzzy name, then hierarchy, with a confidence score and a review queue for the ones that are close.

Automation

SalesforceClearbitMarketoSlack

How to build lead enrichment that does not stall the queue

Enrich on a budget and a timeout, cache by domain, fall back between providers, and never hold a lead waiting for a field.

Automation

ClearbitZoomInfoSalesforceMarketo

How to build lead deduplication and merge

Detect on a scored rule set, survive the merge with field-level rules, keep the activity history, and never silently reassign an owner.

Automation

SalesforceMarketoSlackSnowflake

How to build pipeline hygiene automation

Detect the staleness that matters, nudge the owner rather than the report, escalate on the deals that count, and measure whether it worked.

Automation

SalesforceSlackGongOutreach

How to build a CRM to marketing automation sync

Decide field ownership before you build, sync deltas not everything, handle the person-versus-lead model gap, and break loops.

Integration

SalesforceMarketoSlackSnowflake

How to build a sales engagement to CRM sync

Log activity without flooding the timeline, suppress sequences on the accounts you must not touch, and keep one definition of engagement.

Integration

OutreachSalesforceZendeskGong

How to build a conversation intelligence to CRM sync

Write the few fields a rep will act on, keep every claim linked to its moment in the call, and never let a model set a close date.

Integration

GongSalesforceGoogle CalendarSlack

How to build a quote-to-order integration

Approved quote to signed contract to booked order, with the approval state carried through and amendments handled.

Integration

Salesforce CPQDocuSignNetSuiteSalesforce

How to build an order-to-cash integration

Closed-won to sales order to invoice to cash applied, as a CRM to ERP integration. Idempotent writes, a reconciliation loop, and

Integration

SalesforceNetSuiteSalesforce CPQStripe

How to build a CPQ to ERP sync

Map the product catalogue as data, carry ramps and proration intact, keep both catalogues aligned, and fail loudly on an unmapped SKU.

Integration

Salesforce CPQNetSuiteSalesforceSlack

How to build a billing to CRM sync

Put invoice and payment state where the account team works, without letting the CRM become a second billing system.

Integration

NetSuiteSalesforceStripeSlack

How to build subscription and entitlement provisioning

Turn a signed contract into working access on the day it starts, handle mid-term changes, and never let entitlement drift from what was sold.

Integration

SalesforceNetSuiteOktaGmail

How to build partner deal registration

Check submissions against pipeline in seconds, protect for a fixed window, expire visibly, and settle conflicts with a rule rather than an argument.

Automation

SalesforceHubSpotGmailSlack

How to build a territory and quota sync

Apply a plan on its effective date, keep in-flight deals with their owner, and make coverage visible before anybody signs off.

Automation

SalesforceSnowflakeWorkdaySlack

How to build a commission data to payroll sync

Qualify transactions against the plan, show the working line by line, hold disputes without holding the run, and reconcile before it pays.

Integration

SalesforceNetSuiteGustoWorkday

Questions people ask

What is the difference between an integration and an automation?

An integration keeps two systems agreeing about the same records, like a CRM and an ERP holding the same customer. An automation runs a process across systems, like routing a lead or chasing an invoice. The distinction matters because they fail differently: an integration fails by drifting out of agreement, an automation fails by acting on the wrong thing.

What is in each guide?

The design of one integration or automation, the sequence it runs in, the systems it touches, a set of prompts that build it, the questions people ask about it, and what changes when it runs in production rather than on a laptop.

Do the prompts work in any coding assistant?

They are written for Tray Headless through an assistant like Claude Code, Codex or Cursor. Each stage names the skills it uses, so the assistant researches the connector, builds the workflow and checks it against the known failure modes rather than guessing at a schema.

Do I have to build the whole thing at once?

No. Each guide is staged, and every stage runs on its own. The first gets you connected and reading real data, and you can stop there and come back.

What happens after the assistant has built it?

The same workflow opens in Tray Build, so the team that owns the process can change thresholds, mappings and routing in the visual canvas without going back to an assistant or waiting on a deployment.

Tray Headless

Integrations, automations, agents, MCP tools

Every guide here is built with Tray Headless, and it builds the other two the same way: the same kind of prompts, in the same coding assistant, on the same governed platform. These sixty-eight cover integrations and automations because that is where most teams start, not because the method stops there.

What will you vibe-code?

See what Tray Headless builds