bind.co

What you can build

bind.co turns a user's mailbox into records your application can use: who they work with, what those people are to them, the emails worth sending next, and the business events hidden in their mail, such as expenses. Each record says how sure bind.co is, where it came from, and whether a person has already confirmed it. This page shows what you can build with that, and where to start.

What to build

Start with your users' network: it needs only the profile and contacts scopes, which every application can request, and your users see their own network as soon as they connect.

Build What your users get Scopes Recipe
Map your network Everyone they work with, from their own mail: who each person is, what they are to the user, how close, and when they last spoke profile:read, contacts:read Map your network
A relationship-aware CRM Their clients and partners, found in their mail, with a summary of each relationship and an email ready to send to each profile:read, contacts:read, drafts:write, drafts:send Client re-engagement
Expense capture Receipts and invoices from their mail as expense records, with the source email and file, ready to approve operations:expenses:write, profile:read Expense capture
Document collection A list of what is missing on each record, the documents already in their mailbox that could fill it, and a prepared message to ask for the rest profile:read, operations:expenses:write, drafts:write Document collection

Each recipe gives the scopes, the calls in order, an example answer for each, and the webhooks that keep your screen current, then ends with ideas for other products built the same way. Every scope named :write includes its :read.

How every recipe works

  1. The user connects. They sign in with Google or Microsoft on bind.co's consent screen and approve your scopes; see the Quickstart.
  2. bind.co turns their mail into records. Your endpoint is told by a webhook when the first records are ready, so you never poll.
  3. You read records and show them. Every inferred value carries a bind_inference_confidence, so you choose what to show directly and what to put in front of the user for review.
  4. The user decides. They confirm, correct or reject; bind.co keeps their decision and never overwrites it with later mail.
  5. New mail keeps it current. <type>.completed webhooks tell you when to read again.

Before you start