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)!
Such a zap can make use of the data provided by Anchor on the connected platform (in this example, slack).
Here's an example of the data available for the Invoice Paid trigger:
Below is a list of the currently available Anchor triggers that can be used in Zapier:
Proposal Sent - triggers when a proposal is sent from Anchor.
Proposal Status Changed - triggers when the status of a proposal changes.
Proposal Approved - triggers when a proposal is approved by the client.
Agreement Amended - triggers when an agreement in your account is amended.
Agreement Amendments Approved - triggers when amendments are approved by the client.
Agreement Terminated - triggers when an agreement is terminated.
Proposal Canceled - triggers when a proposal is canceled.
Invoice Issued - triggers when an invoice is issued.
Payout Received - triggers when a payout is received.
Invoice Paid - triggers when an invoice is paid (including manually marking an invoice as ‘paid externally’).
Invoice Status Change - triggers when an invoice's status changes.
Invoice Payment Failed - triggers when an invoice's payment fails.
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.
When testing a Zap by clicking on Zapier's "Test" button, I can only see sample data. Why?
When testing a Zap by clicking on Zapier's "Test" button, I can only see sample data. Why?
When testing an Anchor Zap, Zapier will always pull a sample record by default, which is not taken from your account, regardless of whether the application was run before. This is expected behaviour and will always happen when using Zapier's "Test" function to test the automation.
In order to test the automation with data from your own records, you should enable the workflow and trigger a real event in Anchor that will activate it. The results in Zapier will reflect real data pulled from your account.