Zapier triggers and the data each one sends: reference
Every Zap trigger the Allmoxy app offers, when each one fires and the fields it sends, plus the events that never reach Zapier and how to get them.
The Allmoxy app in Zapier offers a fixed set of Zap triggers, one for each moment Allmoxy sends: new companies, contacts and sign-ups, payments recorded by hand, order status changes, invoices, process starts and ends, tags and employee clock events. This page lists every one with when it fires and the fields it sends, so you can map them in the Zap editor, and ends with the events Zapier never gets and how to send those with a webhook instead.
Applies to: every Allmoxy site with the Zapier module turned on and the Allmoxy app added to your Zapier account. Zapier shows these triggers under the Allmoxy app in the Zap editor; the field names below are as Zapier shows them.
In this article
- Before you start
- New Company Created
- New Contact Created
- New Signup: Business Account
- New Signup: Individual Account
- New Payment
- New Payment by Invoice
- Change Order Status
- New Invoice
- Process Started
- Process Ended
- Tag added to company
- Tag added to order
- Tag deleted from company
- Tag deleted from order
- Employee clock in/out
- Events that do not reach Zapier, and how to get them
- Things to know
Before you start
If you haven't connected your Zapier account to the Allmoxy app yet, do that first: Connect Allmoxy to Zapier and build your first Zap. A Zap trigger here is the event that starts a Zap; it is not an Allmoxy trigger from Settings > Operations > Triggers, and the two have different event lists.
Addresses are broken out into individual pieces (street, city, state, zip and so on) on every trigger that sends them, so you can map each piece separately. Phone numbers arrive as one text field.
New Company Created
Triggers when a new company is created internally via the Add Company page, or through the API. A company that creates itself on your public sign-up page sends New Signup: Business Account instead.
| Field | What it holds |
|---|---|
| Company name | The company's name |
| Company ID | Allmoxy's number for the company |
| The company's email address | |
| Phone numbers | The company's phone numbers |
| Addresses | The company's addresses, broken out into individual pieces (street, city, state, zip, etc) |
| Default shipping method | The shipping method set on the company |
| Invoice receipt method | How the company receives invoices (for example "email") |
No tags and no custom fields are sent on company records.
New Contact Created
Triggers when a new contact is created through the add contact page on a company, or through the API.
| Field | What it holds |
|---|---|
| Username | The contact's login name |
| First Name | |
| Last Name | |
| Middle Name | |
| Addresses | The contact's addresses, broken out into individual pieces (street, city, state, zip, etc) |
| Contact ID | Allmoxy's number for the contact |
| Company Name | The company the contact belongs to |
| Phone Numbers | The contact's phone numbers |
| The contact's email address | |
| Job Title | The job title on the contact record |
| Status | Whether the contact is active |
New Signup: Business Account
Triggers when a new business account (a company) is created through the sign up page on your site, with the first contact that came with it.
| Field | What it holds |
|---|---|
| Company name | The company's name |
| Company ID | Allmoxy's number for the company |
| Invoice receipt method | How the company receives invoices (for example "email") |
| Phone numbers | The company's phone numbers |
| Default shipping method | The shipping method set on the company |
| Addresses | The company's addresses, broken out into individual pieces (street, city, state, zip, etc) |
| Contact username | The first contact's login name |
| Contact first name | |
| Contact last name | |
| Contact middle name | |
| Contact ID | Allmoxy's number for the first contact |
| The email address on the account | |
| Job Title | The first contact's job title |
New Signup: Individual Account
Triggers when a new individual account (a person with no business company) is created through the sign up page.
| Field | What it holds |
|---|---|
| Username | The person's login name |
| First name | |
| Last name | |
| Middle name | |
| Addresses | The person's addresses, broken out into individual pieces (street, city, state, zip, etc) |
| Contact ID | Allmoxy's number for the person |
| Invoice receipt method | How they receive invoices |
| Phone numbers | The person's phone numbers |
| Default shipping method | The shipping method set on the account |
| The person's email address |
New Payment
Triggers when a payment is recorded by hand, with a manual payment method such as check or cash. It will fire once for each invoice that the payment is applied to. Card, bank (ACH) and account-credit payments do not send it; see Things to know for how to catch every payment.
| Field | What it holds |
|---|---|
| Payment ID | Allmoxy's number for the payment |
| Company Name | The paying company |
| Company ID | Allmoxy's number for the company |
| Address | The company's address, broken out into individual pieces (street, city, state, zip, etc) |
| City | The company's city |
| State | The company's state |
| Zip | The company's zip code |
| Reference number | The check number or reference typed with the payment |
| Date | The payment date |
| Amount | The amount of the payment |
| Payment Type | The manual payment method used |
| Memo | The memo typed with the payment |
New Payment by Invoice
Triggers when a payment is recorded by hand, like New Payment, but this trigger fires once for each invoice the payment was applied to, with the amount applied to that invoice and the invoice's ID. Use it when your Zap works invoice by invoice.
| Field | What it holds |
|---|---|
| Payment ID | Allmoxy's number for the payment |
| Invoice ID | The invoice this part of the payment was applied to |
| Company Name | The paying company |
| Company ID | Allmoxy's number for the company |
| Address | The company's address, broken out into individual pieces (street, city, state, zip, etc) |
| City | The company's city |
| State | The company's state |
| Zip | The company's zip code |
| Memo | The memo typed with the payment |
| Reference number | The check number or reference typed with the payment |
| Date | The payment date |
| Amount | The amount applied to this invoice |
| Payment Type | The manual payment method used |
Change Order Status
Triggers when an order status changes. It includes the order info as well as a summary of the items in the order. It fires once per status the order passes, so an order saved several statuses up in one go sends several events, and remake orders arrive here too. There is no previous status field; Date is when the event fired; Status is the raw status code (for example "verified").
| Field | What it holds |
|---|---|
| Status | The new status, as a code such as "ordered" or "verified" |
| Order Number | The order number |
| Order Name | The order's name |
| Company Name | The customer company |
| Contact Name | The order contact |
| Contact Email Address | The order contact's email |
| Product Summary | A summary of the items on the order |
| Subtotal | The order subtotal |
| Tax Amount | The tax on the order |
| Tax Code | The order's tax code |
| Shipping Amount | The shipping charge |
| Total | The order total |
| Date | When the status changed |
New Invoice
Triggers when an invoice is created. For an order, that is the first time the order's invoice gets a charge date: when the order reaches the status the customer company is charged at (its payment term's charge status), falling back to the site's charge status when the company has none. It also fires for credit memos, other charges, finance charges and invoices imported through the API.
| Field | What it holds |
|---|---|
| Invoice ID | Allmoxy's number for the invoice |
| Invoice Name | The invoice's name |
| Invoice Type | Order invoice, credit memo, other charge or finance charge |
| Invoice Date | The invoice date |
| Charge Date | The date the invoice was charged |
| Ship Date | The order's ship date |
| Company Name | The invoiced company |
| Company ID | Allmoxy's number for the company |
| Subtotal | The invoice subtotal |
| Tax Amount | The tax on the invoice |
| Tax Code | The invoice's tax code |
| Shipping Amount | The shipping charge |
| Total | The invoice total |
| Amount Paid | What has been paid on it so far |
| Void | Whether the invoice is void |
| Export Class | The invoice's export class |
| Exported from Sales Orders Queue | Whether it has been exported from the sales orders queue |
| Exported from Invoices Queue | Whether it has been exported from the invoices queue |
Process Started
Triggers when a process is started: an employee clocks in to a labor process on an order. It names the order and the process but not the employee or the time; for those, use an Allmoxy trigger on Order Process Started with a webhook.
| Field | What it holds |
|---|---|
| Order Number | The order number |
| Order Name | The order's name |
| Process Name | The labor process that started |
| Company Name | The customer company |
| Company ID | Allmoxy's number for the company |
Process Ended
Triggers when a process is ended: a clock-out, a one-step process recorded, a batch created or a process applied from a batch, or an open clock closed. Same fields as Process Started, and the same gap: no employee and no time.
| Field | What it holds |
|---|---|
| Order Number | The order number |
| Order Name | The order's name |
| Process Name | The labor process that ended |
| Company Name | The customer company |
| Company ID | Allmoxy's number for the company |
Tag added to company
Triggers when a tag is added to a company, by a person or by an Allmoxy trigger's Add tags action.
| Field | What it holds |
|---|---|
| Tag | The tag that was added |
| Company Name | The company's name |
| Company ID | Allmoxy's number for the company |
| Name | The name on the company record |
| The company's email address | |
| Phone Numbers | The company's phone numbers |
| Addresses | The company's addresses, broken out into individual pieces (street, city, state, zip, etc) |
Tag added to order
Triggers when a tag is added to an order, by a person or by an Allmoxy trigger's Add tags action (Automatically add tags to an order).
| Field | What it holds |
|---|---|
| Tag | The tag that was added |
| Order Number | The order number |
| Order Name | The order's name |
| Order Status | The order's current status |
| Company Name | The customer company |
| Product Summary | A summary of the items on the order |
| Subtotal | The order subtotal |
| Tax Amount | The tax on the order |
| Tax Code | The order's tax code |
| Shipping Amount | The shipping charge |
| Total | The order total |
| Date | When the tag was added |
Tag deleted from company
Triggers when a tag is removed from a company by a person. Tags removed by an Allmoxy trigger's Remove tags action send nothing to Zapier.
| Field | What it holds |
|---|---|
| Tag | The tag that was removed |
| Company Name | The company's name |
| Company ID | Allmoxy's number for the company |
| The company's email address | |
| Company Phone Numbers | The company's phone numbers |
| Addresses | The company's addresses, broken out into individual pieces (street, city, state, zip, etc) |
Tag deleted from order
Triggers when a tag is removed from an order by a person. Tags removed by an Allmoxy trigger's Remove tags action send nothing to Zapier.
| Field | What it holds |
|---|---|
| Tag | The tag that was removed |
| Order ID | Allmoxy's number for the order |
| Order Name | The order's name |
| Order Status | The order's current status |
| Company Name | The customer company |
| Product Summary | A summary of the items on the order |
| Subtotal | The order subtotal |
| Tax Amount | The tax on the order |
| Tax Code | The order's tax code |
| Shipping | The shipping charge |
| Total | The order total |
| Date | When the tag was removed |
Employee clock in/out
Triggers when an employee clocks in or out on their timecard.
| Field | What it holds |
|---|---|
| Date | When the clock event happened |
| Type (in or out) | Whether it was a clock in or a clock out |
| Employee Name | The employee who clocked in or out |
When a contact is set inactive while still clocked in, Allmoxy clocks them out and the name sent is the person who deactivated them, not the employee.
Events that do not reach Zapier, and how to get them
Some moments in Allmoxy are never sent to Zapier: notes, attachments uploaded to an order, output pages signed, products or supplies created, cards about to expire, subscriptions canceled, B2B remote requests and ship date changes. Payments by card, bank or account credit don't reach Zapier either, only payments recorded by hand.
Every one of those is an event an Allmoxy trigger can listen for. Build a trigger on the event at Settings > Operations > Triggers with the Send web request (Webhook) action, and point it at the app directly or at a catch hook address from Zapier's own Webhooks app, so the data still lands in a Zap. The webhook carries the full record (for an order, its items, totals, dates, custom fields, company tags and order tags), which is more than any Zap trigger above sends. Steps and field lists: Send order data to another app with a webhook; the events: Trigger events, conditions and message variables: reference.
Things to know
- New Payment and New Payment by Invoice fire only for payments recorded by hand. Card, bank (ACH) and account-credit payments never send them. To act on every payment, build an Allmoxy trigger on Payment Made (which covers all methods) with an email or webhook action.
- Change Order Status fires once per status passed. An order saved from Bid straight to Shipped sends Ordered, Verified, In Progress, Completed and Shipped in a row, so a Zap that adds a row per event adds five.
- New Invoice fires at the charge status, the first time the invoice gets a charge date, and for credit memos, other charges, finance charges and API-imported invoices too. On a site whose language is not English, order invoices arrive without items and addresses.
- Company records carry no tags and no custom fields. Tags arrive only through the tag added and tag deleted triggers; custom field values are not sent to Zapier.
- An empty date shows as 1970-01-01, and money arrives as formatted text ("1,284.50"), so treat both accordingly in your Zap's filters and formatters.
- Zapier's sample data comes from the last 10 events of each kind sent from your site, which is what the Zap editor offers when you test a trigger.