FlowRunner
PricingContact
Theme
Start Free

Anchor

Payments

Anchor is an autonomous billing and collections platform built on client agreements. Agents draft and publish proposals, track the agreements they become, and watch invoicing and collections run from those agreements.

Verified 1 trigger 89 actions API key available
Anchor website Platform Documentation Capability data verified 2026-08-24
A new engagement is won and the scope is agreed with the client
Agent reads the services, rates, and terms from the deal record
Create Proposal Draft From Template clones the firm's standard structure
Add Service To Draft From Template adds each scoped line with its billing rule
Get Proposal Draft V2 confirms the totals, legal terms, and reference fields
Publish Proposal sends the contract to the client
The engagement owner reviews the published proposal before anyone approves it on the client's behalf

What This Integration Enables

Anchor is built for firms whose contract is the billing engine. Most billing tools treat the agreement as a document you file somewhere and then re-enter as invoice lines. Anchor treats it as the executable object: the services on a signed agreement carry their own billing triggers, and charges come off the agreement rather than off somebody's memory of what was promised. That is why the API is shaped the way it is, with most of its surface devoted to assembling a proposal draft one service, package, bundle item, and legal-terms document at a time.

FlowRunner agents work that assembly pipeline end to end. An agent builds a draft from a template or a structured object, adds services from the firm's service-template library, attaches the right legal terms and custom pages, publishes the proposal to the client, then reads the agreement it becomes and submits charges against it. Where the pipeline crosses from reversible editing into something a client is bound by, human-in-the-loop is the default rather than an add-on.

Without FlowRunner

Scope lives in three places The proposal, the engagement letter, and the billing setup are typed separately and drift apart
Billing waits on a person Nobody bills the new work until someone remembers to configure it
Amendments are informal Added work is agreed in email and reconciled at invoice time

With FlowRunner

One record from quote to charge The draft becomes the proposal, the proposal becomes the agreement, and the agreement is what bills
Billing starts when the contract does Approval produces a live agreement with its services and billing triggers already set
Amendments are recorded as amendments Adding or terminating a service on a signed agreement leaves a typed change on the record

Use Case Scenarios

  • The proposal a closed deal writes for itself

    A deal reaches closed-won in the CRM and the agent picks it up. It calls Create Proposal Draft From Template to start from the firm's standard structure, then walks the scoped services and calls Add Service To Draft From Template for each one so the billing rule comes from the service template rather than from a person retyping it. Fixed-fee bundles get their sub-services through Add Bundle Item. The onboarding checklist attaches with Add Custom Page To Draft, and the master service agreement attaches with Add Legal Terms To Draft. Get Proposal Draft V2 returns the assembled draft for review, and Publish Proposal sends it. Time entries in Harvest and the project skeleton in Asana are provisioned from the same deal record, so delivery and billing describe the same engagement.

  • Amendments that survive the invoice

    Mid-engagement scope changes usually get agreed in a thread and reconciled two months later. Instead, when a change request is approved, the agent calls Get Agreement V2 to read the current services and their typed billing triggers, then calls Add Service To Agreement so the addition is recorded as an amendment against the signed agreement. Work that is finishing gets Terminate Service On Agreement rather than a note. Update Agreement Reference Fields carries the client's purchase order number onto the invoices. A summary posts to the account channel in Slack, so the delivery lead sees the amendment on the day it happens rather than at the next billing run.

  • A billing run that reconciles before it charges

    On the billing day, the agent lists agreements with List Agreements V2, reads each one's services and billing configuration, and calls Submit Charges to raise the invoice. Out-of-scope work approved during the period is added as an ad-hoc item on the same submission. Where a client is owed money back, Add Credit posts the negative charge against the agreement rather than leaving a manual credit note to chase. Export All Agreements Csv feeds the reconciliation sheet in Google Sheets that the controller checks against QuickBooks Online.

Human-in-Loop Highlight

Approve Existing Proposal On Behalf is the operation that turns a proposal into a binding agreement without the client touching anything. It exists for a real reason, because clients sign on calls and by email and somebody has to record that, but it means an agent calling it creates a live agreement that immediately starts billing a client who never clicked approve. Anchor's own escape hatch is narrow: Withdraw Proposal For Editing takes a published proposal back into an editable state, and that is the only way to change a proposal a client has already seen. So the agent never approves on behalf. It assembles the draft, publishes, and then posts to the engagement owner: "Proposal PR-2291 for Northgate Partners is published and awaiting approval. The client confirmed verbally on the 14th per the call note. Approving on their behalf creates the agreement and starts monthly billing at the rate on line 3. Approve on behalf, or wait for the client to sign?" The assembly runs at machine speed. The signature that commits a client to a recurring charge stays with a person who can be asked why.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via email
Human decides
Agent resumes with decision

Agent Capabilities

89 actions

Business

1
  • Get Active Business Returns the Anchor service-provider business the connection is acting as. Used as a connection check and to confirm which firm a workflow is writing to.

Contacts

5
  • List Contacts Lists client businesses with their primary person, company, and status. Filter by status to exclude archived contacts, which cannot be the client on a new proposal.
  • Create Contact Creates a client record and returns its ID. Uniqueness is per email and company name, so the same person under a new company becomes a new contact.
  • Get Contact Reads one contact in full, including the primary person, company details, and whether the record is active, archived, or deleted.
  • Export All Contacts Csv Downloads every contact as CSV for reconciliation against the accounting system.
  • Export Contacts Csv By Ids Exports a named subset of contacts as CSV, which is the form to use after a filtered list so the export matches what the workflow selected.

Proposal Drafts

8
  • Create Proposal Draft The legacy draft creation route, kept so existing flows keep working. New workflows use the object or template forms below.
  • Create Proposal Draft From Object Builds a draft programmatically from a structured object. The route for generating a proposal out of upstream deal data.
  • Create Proposal Draft From Template Clones a saved proposal template into a new draft, so every engagement starts from the firm's agreed structure.
  • Get Proposal Draft V2 Reads a draft in full: services, billing configuration, payment settings, legal terms, and reference fields. The review step before publishing.
  • Update Proposal Draft V2 Updates the draft's own metadata, such as its name.
  • List Proposal Drafts Lists work-in-progress drafts with their status, client, and last update. Used to find proposals that stalled before they reached a client.
  • Export All Drafts Csv Exports active and scheduled drafts as CSV in the bulk import format.
  • Export Drafts Csv By Ids Exports a named subset of drafts as CSV in the same format.

Draft Services and Bundles

10
  • Add Service To Draft Attaches one service to a flat, non-packaged draft.
  • Add Service To Draft From Template Clones a service template into a flat draft, so the billing rule and pricing come from the library rather than from a retyped line.
  • Update Service On Draft Updates a single service on a flat draft.
  • Remove Service From Draft Drops one service from a flat draft before it is sent.
  • Replace All Services On Draft Sets the draft's complete services list in one call. An empty list clears it, so use this only when the full intended set is known.
  • Set Bundle Sets the complete bundle on a flat service, replacing any existing bundle wholesale.
  • Add Bundle Item Adds one priced sub-service to a flat service's bundle, creating the bundle if the service has none.
  • Update Bundle Item Updates a single bundle item on a flat service.
  • Remove Bundle Item Drops one sub-service from a flat service's bundle.
  • Remove Bundle Converts a bundled service back to a plain line item on a flat draft.

Draft Packages

14
  • Add Package To Draft Adds a named group of services to a draft. Packages are how a proposal offers the client a choice between tiers.
  • Update Package On Draft Updates one package's metadata on a draft.
  • Remove Package From Draft Removes a package and its services from a draft.
  • Replace All Packages On Draft Replaces the draft's packages list wholesale.
  • Add Service To Package Appends one service to an existing package on a draft.
  • Add Service To Package From Template Clones a service template into an existing package, keeping pricing consistent with the library.
  • Update Service In Package Updates a single service inside a package.
  • Remove Service From Package Removes one service from a package.
  • Set Bundle In Package Sets the complete bundle on a service inside a package, replacing any existing bundle.
  • Add Bundle Item In Package Adds one priced sub-service to a packaged service's bundle, creating the bundle if absent.
  • Update Bundle Item In Package Updates a single bundle item on a service inside a package.
  • Remove Bundle Item In Package Drops one sub-service from the bundle of a service inside a package.
  • Remove Bundle In Package Converts a bundled service inside a package back to a plain line item.
  • Ungroup Draft Package Converts a single-package draft back into a flat services list by promoting the package's services and clearing the package. Services mode and packages mode are mutually exclusive, and this is the way back.

Draft Custom Pages

7
  • Add Custom Page To Draft Appends a text, PDF, or video page that the client sees alongside the proposal. Used for onboarding notes, scope appendices, and case material.
  • Update Custom Page On Draft Updates one custom page on a draft.
  • Remove Custom Page From Draft Deletes one custom page so it no longer appears to the client.
  • Replace All Custom Pages On Draft Replaces the draft's custom pages list wholesale.
  • Get Custom Page Text Returns the rendered HTML body of a text custom page, given the text handle from a draft or agreement.
  • Get Custom Page Pdf Upload Url Returns a presigned upload URL, called before a PDF custom page is added to a draft.
  • Get Custom Page Pdf Download Url Returns a one-time download URL for the PDF backing a custom page.

Draft Legal Terms

4
  • Add Legal Terms To Draft Attaches one legal-terms document from the firm's library to a draft.
  • Update Legal Terms On Draft Changes how an attached document appears on this draft, without touching the shared library or any other draft.
  • Remove Legal Terms From Draft Removes one attached legal-terms entry from a draft.
  • Replace All Legal Terms On Draft Replaces the draft's attached legal-terms list wholesale.

Legal Terms Library

7
  • List Legal Terms Lists the terms of service, privacy policies, and master service agreements the firm has authored or uploaded, with each entry's type.
  • Create Rich Text Legal Terms Creates a new legal-terms document from rich-text content.
  • Update Rich Text Legal Terms Updates a rich-text document's name and content. Changes here affect what future proposals attach.
  • Create Pdf Legal Terms Creates a legal-terms document backed by an uploaded PDF.
  • Update Pdf Legal Terms Replaces the PDF behind an existing document and updates its display name.
  • Get Legal Terms Pdf Upload Url Returns presigned upload URLs, one per file and in the order supplied, for new PDF legal-terms documents.
  • Get Legal Terms Pdf Download Url Returns a presigned download URL for the PDF behind a legal-terms document.

Service Templates

5
  • List Service Templates Lists the reusable service templates with their billing and pricing. The library a proposal should be built from.
  • Create Service Template Service Creates a standalone service template with its billing configuration and pricing.
  • Create Service Template Bundle Creates a bundle grouping existing service templates under combined billing. Members must be services rather than other bundles.
  • List Service Templates Legacy The deprecated single-response listing, kept for existing flows. New work uses the paginated listing.
  • Export Service Templates Csv Exports service templates as CSV with their pricing, billing, and discount columns.

Proposal Templates

3
  • List Proposal Templates Lists the pre-configured proposal structures the firm starts from.
  • Get Proposal Template V2 Reads a template in full: services, packages, payment settings, and legal-terms references.
  • Delete Proposal Template V2 Soft-deletes a proposal template owned by the business.

Proposals

9
  • Publish Proposal Publishes a draft as a proposal and notifies the client. The step where an internal document becomes something a client is reading.
  • List Proposals Lists proposals with status, client, expiration, and progress. Used to find contracts sitting unanswered.
  • Get Proposal Reads the full details of a proposal sent to a client for approval.
  • Approve Existing Proposal On Behalf Approves a sent proposal for the client, vendor-initiated. This creates the agreement that bills, which is why this page's human gate sits here.
  • Withdraw Proposal For Editing Withdraws a published proposal so its linked draft becomes editable again. The only route to changing a proposal the client has already seen.
  • Cancel Proposal Edit Discards the linked draft's pending edits and restores the proposal to its pre-withdrawal state.
  • Republish Proposal Applies the linked draft's edits and re-sends the proposal to the client.
  • Export All Proposals Csv Exports awaiting-approval and expired proposals as CSV.
  • Export Proposals Csv By Ids Exports a named subset of proposals as CSV.

Agreements

11
  • List Agreements Lists agreements with name, status, client, and effective date.
  • Get Agreement Reads full agreement details: services, billing configuration, and payment settings.
  • List Agreements V2 The v2 listing, whose payload matches v1. The entry point for a billing run.
  • Get Agreement V2 Reads the v2 shape, which adds typed billing triggers, pending amendments as post-amendment snapshots, a signing audit, and the client's selections.
  • Add Service To Agreement Adds a service to a signed agreement as a new amendment, which is how in-flight scope growth becomes billable and recorded at once.
  • Update Service On Agreement Updates a single service on a signed agreement.
  • Terminate Service On Agreement Terminates one service on a signed agreement, effective immediately. Used when a workstream ends without ending the engagement.
  • Update Agreement Settings Patches net terms, credit card fees, billing day, and amendments policy on an agreement.
  • Update Agreement Reference Fields Replaces the full set of reference fields, such as a client purchase order number, on a signed agreement. This is a replacement, so send the complete set.
  • Export All Agreements Csv Exports every agreement as CSV, one row per service, with billing, payment status, and contacts.
  • Export Agreements Csv By Ids Streams a CSV export of specific agreements by ID.

Billing

2
  • Submit Charges Submits charges against an agreement to generate an invoice, either immediately or scheduled for a future billing date. Ad-hoc out-of-scope items can ride along.
  • Add Credit Adds a credit against a client's account under a specific agreement, reducing what future invoices collect. Used for refunds, goodwill, and prepayment adjustments.

Webhooks

3
  • List Webhook Subscriptions Lists the active webhook subscriptions with each target URL and the events it receives.
  • Subscribe Webhook Creates or replaces a subscription for a target URL and returns the key that authenticates its deliveries. Subscribing replaces that URL's whole event list, so send every event you want.
  • Unsubscribe Webhook Deletes a subscription by ID so its target URL stops receiving events.

Triggers

1 triggers

Event Triggers

1
  • On Anchor Event Fires on Anchor's proposal, agreement, invoice, and payout events, including wildcards that cover a whole family at once. A collections workflow usually wants the invoice family rather than a dozen separate subscriptions, so a payment state change starts the follow-up without anyone polling for it.

Frequently Asked Questions

What can FlowRunner do with Anchor?

FlowRunner agents can run List Agreements, Get Agreement, and Add Credit in Anchor, plus 86 more actions.

Does connecting Anchor to FlowRunner require OAuth?

No. Anchor connects to FlowRunner with an API key, no OAuth flow required.

Can Anchor trigger a FlowRunner workflow automatically?

Yes. Anchor supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with Anchor

Free plan, no card required. Connect in minutes.