The following new triggers are available for use in Zaps using Avochato for Zapier v1.20.

Triggers whenever a ticket/conversation changes from any one status to another. Some examples of when ticket statuses change:

Includes information about the ticket, the contact, and the most recent message in the conversation (if any).

Triggers when a new outbound message gets sent from an inbox.

Includes info about the message, any MMS contents (if applicable), the ticket, and the contact.

Triggers when a contact opts out or is marked as opted out in Avochato.

Includes the contact info and optionally the message contents (if opting out via a “stop” keyword).

Triggers when a contact opts in or is marked as opted in in Avochato..

Includes the contact info and optionally the message contents (if opting in via a “start” keyword).

The following new triggers are available for use in Zaps using Avochato for Zapier v1.20.

Adds a tag to a specific contact. Tag names are case-sensitive and searchable in the inbox.

Removes a specific tag from a contact - tags are case-sensitive, and must match exactly.

Remove a specific contact(s) from a specific campaign(s). You can pass more than one contact by their ID or phone number via the “contacts” or “phone” parameters, respectively, and specify one or more campaign steps to remove them from by providing the campaign keyword (or a comma-separated list of campaign keywords).

Additionally, we have two new power features for mass-manipulating campaigns:

We’ve added new fields to the “send a message” action.

Optional - Must be a unix timestamp e.g. 1735718399

Schedule this message for a time in the future. Leave this field empty and the message will send as soon as this action is triggered. To convert a date to a UNIX timestamp using the Zapier Formatter, learn more here

When we send this message, mark the conversation as addressed.

Defaults to false.

Optional - send this message from a specific Avochato number you own in this inbox. By default, we send the message from the Avochato number this contact is currently texting with. If this contact has never been contacted before, we will round-robin through your existing Avochato numbers in this inbox. The contact will receive this text message from this number on their device.

Must be a valid Avochato number that belongs to this inbox, using E.164 format e.g. +1 415 222 33 44

Email address of an Avochato user that you want to send this message on behalf of.

This message will appear as if it was sent by this user when viewing the inbox. If your inbox is configured to assign conversations on outbound messages, and the conversation is currently unassigned, it will re-assign this conversation to that user.

Must be a valid email that exactly matches a user in this Avochato inbox user list.

All of the following optional fields have been added, and can be set in new or existing Zap actions.

Make a specific user the “owner” of a contact in this inbox. Avochato will assign conversations with this contact to this Avochato user by default. Can either be the email address or the hash ID of a user in your Avochato inbox.

Tip: you may also assign AvoBot users as “owners” which will route all conversations to the Avobot by default.

If passing an email address, the email must match exactly and must be the email of a user or AvoBot that has already been added to this inbox via the Invite Users tab.

Optional, Defaults to empty.

The priority level of this contact. 1 is the lowest, 5 is the highest.

You can optionally sort your inbox by priority to handle higher priority contacts before lower priority ones.

High priority contacts show up higher in your contacts list and can bypass robocall protection, among other things.

Optional, defaults to 0 (no priority)

Whether or not calls or texts from this contact trigger any alerts or notifications in Avochato. Muted contact activity is still visible in your inbox and logs, and you can still make calls or texts to this contact.

Optional, Defaults to false.

Whether or not you have blocked this contact. Calls and messages from blocked contacts will never appear in your inbox. Used for preventing harassment or spam. The contact will still appear in your contacts list.

Optional, Defaults to false.

Optional, Defaults to false. Indicates whether this contact has manually opted out from receiving text messages or not.

Contacts that have opted out will be prevented from receiving outbound text messages from your Avochato numbers, per TCPA compliance. Your contacts can text START to your Avochato number to automatically opt in, or STOP to opt out.

Whether this contact has ever texted an affirmative double opt in keyword to this inbox.

Inboxes can be configured to require affirmative consent before sending dynamic text messages via SMS. If a contact would receive an outbound message from your number, instead they are asked to reply with a custom double-opt-in keyword (ex: "Text YES to confirm you want to receive updates". Once a contact replies with YES, they will be marked as double opted in and receive the double-opt in confirmation auto-response.)

Double opt in keywords and responses can be configured in Account Settings.

For more information on Double Opt In, read more here

Optional, Defaults to false.

Visible contacts appear in your “all contacts” list. When you delete a contact via the Avochato app, they are no longer visible and do not appear in the contacts list by default, will not be included in any bulk actions (such as “add all contacts to a broadcast” or “add via tag” etc). They can be restored in the future by setting visible to true via the app or API.

Note: marking a contact as no longer visible does not delete conversations or message logs.

Optional, Defaults to true.

If you have connected Avochato to a Salesforce instance, this is the ID of the record that we will sync data to. Must be a valid Salesforce ID that matches the Object Type.

Optional. Defaults to empty, and will be populated automatically when syncing records to Salesforce unless manually updated. Requires a valid salesforce_object_type to bet set in order to work.

The Object Type to use when syncing records to this contact in Salesforce.

Must be a valid object type that exists in your inbox's connected Salesforce instance. e.g. "Contact", "Lead, etc

Optional. Defaults to empty. If passing a Salesforce Object ID, it defaults to "Lead" unless otherwise customized in your inbox's Salesforce Settings page.

Optional, requires format +14152223344.

If you have connected more than one Avochato number to your inbox, you can "stick" this contact to specific Avochato number to automatically send all future outbound texts from that number.

Contacts automatically "stick" to the last number they sent an inbound text message to in your inbox. If there is no stuck number for a contact, Avochato will randomly choose one of your Avochato numbers when delivering an outbound message, and stick them to it if they respond.

Defaults to empty. This number must belong in your list of Avochato numbers in this inbox.

Optional, Defaults to false. Allows overwriting data in contact custom fields when updating a contact.

When true, any custom fields that are not filled in as part of this zap will overwrite the corresponding custom field data for this contact. Ex: if your contact has a "favorite_ice_cream" field set to "strawberry", and you pass "favorite_ice_cream": "", we will clear their "favorite_ice_cream" field when attempting to update this contact.

Does not apply when creating new contact records.

Note: only enable this if you are confident all the custom field data passed by zapier should always overwrite whatever is in Avochato, even if the custom field value is empty. This can result in loss or corruption of custom field data which cannot be recovered.