We need to divide messages received on Salesmsg (we have all emails there linked to phone numbers) based on which group on the Monday.com board that email address is in, and then notify two different Slack channels.For example, if the email of the person who sent a text in Salesmsg is in the group "Sales contacts", notification must arrive in one Slack channel, but if email is in the group "Product contacts", it should arrive in another channel.
With using filter Monday.com colums, all are getting transformed to text, so it is not just email. There are other symbols too, and that is why "contains" and "exactly matches" filters don't work. What is the best solution here?
Best answer by christina.dView original
Perhaps you can outline a specific data example for us to have more context about the filtering issue.
@Troy Tessalone, this is overall set-up:
We need to send notifications ONLY sender’s email (or phone number either works for us) is in the particular group on Monday.com board. But filter is not working properly. Here is the error we get:
We tried to put “Is not in” filter too, but it just sends all messages to the Slack channel without sender’s email group check. Is it possible to do thing like this in Zapier at all?
The way the Filter condition is currently configured will never evaluate to true, thus the Zap will never pass the Filter step.
The condition is trying to compare a Contact email address value to a Monday Board Group ID value.
For Step 2 in the Zap, you probably want to use this Monday action: Get Item by Column Value
You’d use this to search for the Contact’s email address on the Monday Board, which will return the corresponding Monday Board Group for the found Item.
Then in the Filter step, you probably want your condition to be like this:
[Group ID] contains “XXX”
You can use Paths instead of a Filter step to handle both routes (Groups)
Filter help article: https://zapier.com/help/create/customize/filter-and-path-rules-in-zaps
and it only brings “Tags” column all the time
How is your Step 2 configured now?
Try this...once you found the desired Monday Item, then add another Monday step to get all of the Item column values
Those are options, and we can’t choose anything from the previous step as that is not normal text-data, that is fulfilment data
We need to divide it depending on which group the email address is in (there is one particular group that we need to divide the most)
You can use the Custom option to map dynamic variables between Zap steps.
Logic is this…
@valeriasem! Just wanted to check in here to see if you were able to get things set up with Troy’s last suggestion. Let us know - we want to make sure you’re good to go here!
@jesse and @Troy Tessalone
No issue is still there on our side. This set up:
Only “Custom” fields available from the second step are fulfilment data ones:
There is no dynamic Item ID column available. In the second step column to search in is the email:
In Step 2, you need to map a value from Step 1 to the Email field to search by.
Did you successfully test step 2?
If an Item was found in step 2, then the Item ID will be returned to use for mapping to other Zap steps.
Those are from step 3:
*assets is not a group name
Unfortunately, it looks like with the newest version of the Monday Zap app that some previously available data points are no longer available. (e.g. Group ID)
You’ll likely have to use the Monday GraphQL API to derive the desired data points: https://api.developer.monday.com/docs
App APIs can be used in Zaps with the Webhook app: https://zapier.com/apps/webhook/help
If you need help, consider hiring a Zapier Expert: https://zapier.com/experts
Hey there, I wanted to pop in and mention it appears
@valeriasem is being impacted by a known bug with the Monday app where Group ID values won’t load when a dynamic value is set for the Board ID. 😔
I went ahead and added them to the impacted user report and we’ll be in touch once a fix is in place! We’ll also be sure to update the topic as well. 🙂
Thanks for your patience while we dug into this one!
Hey squad! I wanted to pop in and let ya’ll know this bug has officially been closed! 🎉
@nicksimard being the wizard ✨ he is even put together this article on mapping fields to dynamic dropdown fields. Check it out here:
Thanks for your patience on this one!