Close, ready to run.

The Close integration brings operations into your sales CRM. Floowed reads the lead, its contacts and its opportunities, checks a case against your rules, and writes the outcome back to the lead where your reps will see it.

What it is
Close is a sales CRM built around leads, with calling, email and pipeline management in one place.
Connects by
An API key over HTTP Basic auth, or OAuth 2.0 for an installed app
Category
CRM

What it does.

What Floowed reads from Close

  • Leads and the contacts on them
  • Opportunities, with their status and value
  • Activities such as notes, emails and calls
  • Custom fields on leads and opportunities

What it writes back

  • Custom field values recording the outcome
  • A note on the lead explaining what was decided and why
  • A task for the rep when a person needs to act
  • An updated lead or opportunity status, where your rules allow

In Close, everything hangs off the lead, so write the outcome there and it shows up in the reps' smart views. A typical operation is checking a new customer after a deal is won, before onboarding starts.

A new customer handover, from won deal to first invoice.

  1. Gather

    A rep marks an opportunity won in Close. Floowed opens the case, reads the lead, its contacts and the notes, and asks the customer for the documents onboarding needs.

  2. Interpret

    Floowed reads the signed order form and the company documents, and checks the legal name, billing details and terms against what the rep recorded.

  3. Chase

    A missing tax form goes back to the customer by email. A term that differs from the order form goes to the rep as a task on the lead.

  4. Decide

    Your handover rules run in the deterministic policy engine. Anything outside them goes to finance to decide.

  5. Act

    Floowed creates the customer and first invoice in Xero, posts the handover to the delivery team in Slack or the Floowed Dashboard, and writes the outcome to custom fields and a note on the Close lead.

Used in the same case

The connection, in detail.

Authentication
An API key over HTTP Basic auth, or OAuth 2.0 for an installed app
Access
A key or token acts as the Close user it belongs to, with that user's access to the organization
New cases from
A webhook subscription on lead or opportunity events, signed with an HMAC signature
API
Close REST API v1

How it connects.

  1. 1

    Connect Close

    Using an API key over HTTP Basic auth, or OAuth 2.0 for an installed app. Nothing migrates and nothing is replaced.

  2. 2

    Build your operation

    Describe it in Slack, Teams or the Floowed Dashboard. Floowed builds it and asks only what it can’t work out.

  3. 3

    Let it run

    Every case runs from request to outcome, the same way each time, with the reasons on record. Anything sensitive waits for a person.

Questions

Does Floowed integrate with Close?

Yes. Floowed connects through the Close REST API, with an API key or over OAuth 2.0, and works with leads, contacts, opportunities, activities, tasks and custom fields.

How does a case start from Close?

Through a webhook subscription, for example when an opportunity changes status to won. Close signs each webhook with an HMAC signature, so Floowed can check it came from Close.

What can Floowed write back to Close?

Custom field values with the outcome, a note on the lead explaining what was decided and why, a task for the rep when a person needs to act, and lead or opportunity status changes where your rules allow.

What access does Floowed get?

Close API keys and OAuth tokens act as a Close user. Connect with a dedicated user whose role covers only what the operation needs. Every case keeps a full record of what was read and written.

What does the Close integration cost?

Nothing extra. Integrations are included, and you pay for the work Floowed does on a case. Start free with $80 of credits, no card and no sales call.

Start with Close. Add the rest.

Free to try, no card, no sales call. Your first $80 of credits is on us.