Reference · built on requestOperator by FibricSales, quotes & revenue

Deal Handoff

When a deal is won, drafts the ERP customer, payment terms, and onboarding tasks from the deal and quote and proposes them for setup.

Request accessPricing ↗

About

Deal Handoff starts the moment a deal is marked won in the CRM. It collects the deal, the accepted quote and its line items, and the billing contact and company attached to the deal. It then checks the ERP for a customer that already matches by name, email, or tax registration number.

From that it drafts three things for setup: the ERP customer record with currency and address filled in, the payment terms and credit limit for finance to confirm, and the onboarding tasks from your template with owners and due dates. Finance and operations each approve their part. Nothing is created until they do.

This is a reference listing. It documents what Fibric would read from Deal Handoff and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Deals reaching a won stage: HubSpot UPDATE webhooks on dealstage, with dealname, amount, closedate, and hubspot_owner_id
  • Pipedrive deals whose status turns won, with won_time, and Salesforce opportunities through Change Data Capture
  • The accepted quote behind the deal: a HubSpot quote in APPROVED state with its line items, or a Business Central salesQuote with acceptedDate
  • Contacts and companies associated to the deal, for the billing contact, address, and tax registration number
  • Existing ERP customers, matched on displayName, email, and taxRegistrationNumber, so a returning customer is linked rather than duplicated
  • Payment terms, currencies, and shipment methods the ERP already defines, read by paymentTermsId, currencyCode, and shipmentMethodId
  • Onboarding project templates: Asana projects with sections and custom fields, or Jira projects and issue types

Proposed actions

  • Target capability: propose a new ERP customer through POST customer, with displayName, address, email, currencyCode, and paymentTermsId filled from the deal
  • Target capability: propose the payment terms and creditLimit for the new customer, shown beside the terms on the quote, for finance to confirm
  • Target capability: propose the onboarding tasks through POST /tasks in Asana or POST /rest/api/3/issue in Jira, each with an owner and due_on
  • Target capability: propose converting the accepted quote to an order through the salesQuote makeOrder action once the customer exists
  • Target capability: propose a task on the deal for its owner listing the customer number and tasks created

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • HubSpot closed-won to a Business Central customer

    On the dealstage webhook, read the APPROVED quote and its line items, match or draft the Business Central customer with paymentTermsId and currencyCode, and propose makeOrder once finance signs off.

    With HubSpot, Microsoft Dynamics 365 Business Central

  • Pipedrive win to QuickBooks and Asana

    When status turns won, draft the QuickBooks Online Customer with its payment terms and propose the onboarding tasks in the Asana project, each with an assignee and due_on.

    With Pipedrive, QuickBooks Online, Asana

  • Salesforce opportunity to NetSuite and Jira

    Read the won opportunity through Change Data Capture, propose the NetSuite customer and terms, and open the onboarding issues in Jira from your template with owners set.

    With Salesforce Sales Cloud, NetSuite, Jira

  • Announce the handoff

    Post the customer number, terms, and task links to the account team in Slack once both approvals are in.

    With Slack

Requirements

  • A CRM that emits deal stage changes: HubSpot webhooks, Pipedrive webhooks, or Salesforce Change Data Capture
  • An ERP whose customer record can be created by API, such as Business Central, QuickBooks Online, NetSuite, or Acumatica
  • A work tool with an onboarding project or issue type to copy from: Asana, Jira, or monday.com
  • An approver in finance for terms and an approver in operations for the onboarding tasks
Authentication
CRM webhooks and API reads through an OAuth app or private-app token, an ERP API user allowed to create customers, and a work-tool token with task write scope.

Limits

  • It drafts the customer record and the tasks. It never posts an invoice, takes a payment, or ships an order.
  • A won deal with no accepted quote or no billing address produces a proposal with the gaps marked, not a customer record.
  • Duplicate detection reads the customer fields your ERP exposes. A customer filed under a different trading name can slip past and needs a person's eye.
  • Credit limits are proposed from what your team already recorded on the deal. It runs no credit check.

Access and pricing

Reference listing. Fibric builds the operator under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request Deal Handoff ↗

Questions and answers

Who approves what?
Two things, separately. Finance approves the customer record with its terms, currency, and credit limit. Operations approves the onboarding tasks with owners and due dates. Either can edit before approving. Nothing is written to the ERP or the work tool until both have.
What if the customer already exists in the ERP?
The proposal links the existing customer instead of creating one and lists the fields where the deal and the record disagree, such as address or email. A person picks which value to keep. No merge happens on its own.
What record is left after a handoff?
The deal id, the quote id, the customer number created or matched, the terms approved, each task created with its id, who approved each part, and when. Every created record carries a note pointing back to the deal, and the entry says how to reverse each one.
Ask about Deal Handoff

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This operator is developed, published, and supported by Fibric. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy