Using Add and Remove Tag Flow actions

Use Salesforce Flow to automatically add and remove Avochato Tags

Avochato Tags are a fantastic way to segment and categorize your Avochato conversations / contacts.

You can use Avochato - Add Tag or Avochato - Remove Tag Flow automation actions to add and remove Avochato Tags based on your ever changing Salesforce data.

Notion image

Flow action options

Both the “Avochato - Add Tag” and “Avochato - Remove Tag” flow actions require the tag to be specific, and then require either the phone or ids parameters to specify the Avochato Contacts that should receive the tag.

Notion image
  1. (Required): tag - The tag to add or remove from the Avochato Contact. You can add multiple tags by making a comma , separated list of tags.
  1. ids - The Avochato Contact Id of the Avochato Contact that you want to tag. This can be a comma separated list of Avochato Contact Ids. If there are multiple requests within the same Flow transaction, we auto-magically bulk the requests into a single API callout, avoid API limitings in Salesforce & saving on Avochato API resources.
  1. phone - The phone number to use in order to match the Avochato Contact and tag that contact. When using phone, we make an API callout for each request, and Salesforce orgs will be held to the normal limits of making API callouts using Flow builder automation (i.e. max 10 API callouts in a single transaction, or 50 max when using async processing like future or queueable callouts).

Use case - Tagging based on Salesforce Leads

When phone and ids are both specified, the ids takes precedence and the phone parameter is ignored. This means you can pass both ids and phone parameters, and depending on the Salesforce data, it’ll process whichever one is present.

Notion image

For example, if may have different sources of SF lead generation, like having Avochato generated leads that automatically sync the Avochato Contact Id to the lead, vs. leads created through CSV imports, or other connected systems. You can populate both ids and phone in the Flow action, and if only phone is populated, we’ll attempt to sync to the Avochato Contact via a phone match. If ids is populated, then it’ll be a more precise matching to the Avochato Contact.

If one of the ids is an invalid Avochato Contact Id (maybe it was deleted, or belongs to a different Avochato inbox, etc), then the API callout will fail to update the tags across any of the ids.
Did this answer your question?