What Anchor zaps can I create?
Every Zap that Zapier supports, including Anchor zaps, combines a trigger from one product with an action from another. Zapier automatically completes the action whenever the trigger occurs.
Go to our Integration page in Zapier to connect your other apps to Anchor in minutes!
As an example, you can set up a Zap to send you a Slack message (action) whenever an invoice has been paid (trigger), and use the invoice data returned by Anchor to populate that message.
On 05/20/2026 we overhauled the Zapier integration to support more actions and triggers. If you've already connected to Zapier before then, please follow the steps in this video to connect to the new version.
Triggers
Triggers fire instantly when the selected event occurs in Anchor. The following triggers are available:
Agreement triggers
Agreement triggers
Agreement Amended: triggers when an agreement is amended.
Agreement Amendments Approved: triggers when amendments to an agreement are approved.
Agreement Terminated: triggers when an agreement is terminated.
Invoice triggers
Invoice triggers
Invoice Paid — triggers when an invoice is paid in full (either collected by Anchor or marked paid externally).
Invoice Payment Collected — triggers when payment for an invoice is collected (Anchor received the funds, before settlement).
Invoice Payment Disputed — triggers when an invoice payment is disputed by the client.
Invoice Payment Failed — triggers when payment for an invoice fails.
Invoice Payment Initiated — triggers when payment for an invoice is initiated (a charge is in flight).
Invoice Payment Partially Refunded — triggers when an invoice payment is partially refunded.
Invoice Payment Refund Failed — triggers when refunding an invoice payment fails.
Invoice Payment Refunded — triggers when an invoice payment is refunded in full.
Invoice Voided — triggers when an invoice is voided.
New Invoice Issued — triggers when a new invoice is issued.
Proposal triggers
Proposal triggers
New Proposal Sent — triggers when a proposal is sent to a client.
Proposal Approved — triggers when a proposal is approved. The payload is the resulting agreement (a proposal becomes an agreement on approval).
Proposal Expired — triggers when a proposal expires before being approved.
Proposal Published — triggers when a proposal is published.
Proposal Reviewed — triggers when a proposal is reviewed by the client.
Proposal Withdrawn — triggers when a proposal is withdrawn by the service provider.
Payout triggers
Payout triggers
Payout Deleted — triggers when a payout is deleted.
Payout Failed — triggers when a payout fails.
Payout Paid — triggers when funds are paid out to your bank.
Actions
Actions let you create records or look up existing ones in Anchor from within a Zap.
Create
Create
Add Credit to Agreement — issues a credit on an agreement.
Create Contact — creates a new client contact in Anchor.
Create Proposal Draft From Template — clones a saved proposal template into a new draft. Usually chained with Publish Proposal.
Publish Proposal — publishes a proposal from an existing draft and sends it to the client for approval. Typically chained after Create Proposal Draft From Template.
Search
Search
Find Agreement by ID — looks up a single agreement by its Anchor ID.
Find Contact by ID — looks up a single contact by its Anchor ID.
Find Invoice by ID — looks up a single invoice by its Anchor ID.
Find Payout by ID — looks up a single payout by its Anchor ID.
Find Proposal by ID — looks up a single proposal by its Anchor ID.
List Agreements — returns your most recent agreements in Anchor.
List Contacts — returns your most recent contacts in Anchor.
List Invoices — returns your most recent invoices, optionally filtered by status or agreement.
List Payouts — returns your most recent payouts in Anchor.
List Proposals — returns your most recent proposals in Anchor.
Data returned by triggers and actions
The fields below show the data available for some object types. For triggers and actions not listed here, you can see the full field set by testing them directly in Zapier with your own account data.
Agreement triggers
Applies to: Agreement Amended, Agreement Amendments Approved, Agreement Terminated, and Proposal Approved (which returns an agreement object).
Group | Fields |
Agreement | ID, Agreement Name, Status, Effective Date, Last Updated At, PDF Link, Link |
Client – Primary Contact | Email, First Name, Last Name, User ID, Has Signed |
Client – Business | Business ID, Business Name, Contact ID |
Service Provider – Assignee | Email, First Name, Last Name, User ID |
Service Provider – Business | Business ID, Business Name |
Connected Payment Method | ID, Last 4, Type |
Agreement Settings | Terms of Service ID & Name, Terms of Service Documents, Amendments Approval Method, Invoices Approval Method |
Services | ID, Name, Billing Occurrence, Billing Trigger, Billing Day of Month, Is Billed Upfront, Pricing Type, Price, Price After Discount, Discount Type & Amount, Service Template ID, Status, Has Pending Amendments, Is Paused, Prorate First Payment, Automatic Price Increase (Enabled, Increase On, Round Prices, Percent), Max Charges (Type, Limit, Charges Left) |
Payment Settings | Require Client Payment Approval, Credit Card Fees Paid By, Net Terms |
Invoice triggers
Applies to: Invoice Paid, Invoice Payment Collected, Invoice Payment Disputed, Invoice Payment Failed, Invoice Payment Initiated, Invoice Payment Partially Refunded, Invoice Payment Refund Failed, Invoice Payment Refunded, Invoice Voided, New Invoice Issued.
Group | Fields |
Invoice | ID, Invoice Number, Issue Date, Due Date, Total Amount, Amount Paid, Amount Due, Amount Refunded, Status, Net Terms, Can Retry Payment, Created At, Link |
Detailed Status | Type, Additional Info Type |
Agreement | Agreement ID, Agreement Name |
Client – Business | Business ID, Business Name |
Service Provider – Business | Business ID, Business Name |
Integrations | QuickBooks Status, Xero Status |
Line Items | ID, Name, Description, Quantity, Rate, Discount, Amount, Unit Name, Note, Service ID, Service Template ID, QuickBooks Integration, Xero Integration, Period, Sub Items |
Proposal triggers
Applies to: New Proposal Sent, Proposal Expired, Proposal Published, Proposal Reviewed, Proposal Withdrawn.
Group | Fields |
Proposal | ID, Agreement Name, Status, Progress Status, Effective Date, Last Updated At, PDF Link |
Client – Primary Contact | Email, First Name, Last Name, User ID, Has Signed |
Client – Business | Business ID, Business Name, Contact ID |
Service Provider – Assignee | Email, First Name, Last Name, User ID |
Service Provider – Business | Business ID, Business Name |
Connected Payment Method | ID, Last 4, Type |
Agreement Settings | Terms of Service Documents, Amendments Approval Method, Invoices Approval Method |
Services | ID, Name, Billing Occurrence, Billing Trigger, Billing Day of Month, Is Billed Upfront, Pricing Type, Unit Cap, Price, Price After Discount, Discount Type & Amount, Service Template ID, Inclusion Type, Do Not Start Automatic Billing, Prorate First Payment, Automatic Price Increase (Enabled, Increase On, Round Prices, Percent), Max Charges (Type, Limit, Charges Left) |
Payment Settings | Require Client Payment Approval, Credit Card Fees Paid By, Net Terms, Require Payment Method |
Proposal | Reviewers, Signatories, Primary Contact Link |
Contact actions (Find Contact by ID, List Contacts)
Group | Fields |
Contact | ID, Created At, Company Name, First Name, Last Name, Email, Phone, Status, Is Sample |
IDs | Vendor ID, Customer ID, User ID |
Account State | Has Signed Agreements, Has Pending Proposals, Has Drafts, Version |
Permissions | Accountant Access, Edit Mode, Is Email Editable, Is Multi Vendor Customer, Has Vendor Relation |
Eligibility | Archive Eligibility Type, Delete Eligibility Type |
For payout triggers and all other actions not listed above, connect your Anchor account in Zapier and use the Test step to see the full field set with your own live data.
Frequently asked questions
After duplicating (or updating) a Zap, why do some fields show a "!" warning, disappear, or stop populating values - and how do I fix it?
After duplicating (or updating) a Zap, why do some fields show a "!" warning, disappear, or stop populating values - and how do I fix it?
This usually happens because when you duplicate a Zap, Zapier creates a new trigger step ID but may still reuse the old test/sample record from the original Zap.
Since Zapier derives the available fields (and their names) from that sample data, later steps - especially Filters - can show missing fields, warning icons, or empty values (for example, "Services Name" disappearing and only "Name" showing).
This isn't an Anchor schema change - just stale sample data. To fix it, open the duplicated Zap, go to Step 1 (the trigger), and click Test / Find new records to load fresh data. Then return to the step with the issue and reselect the field; it should appear again.
Best practice: After duplicating a Zap, re-test the trigger right away before adjusting mappings. If the field still doesn't show, try a different recent test record that definitely includes the data you need, or re-add the affected step after refreshing the trigger sample.