match post with relevant user

Sorry @hmc , doing the match based on zip code is no problem (assuming this is stored in post meta), but matching something based on a “radius” isn’t something Automator could help with. We can’t do any type of geocoding.

There are some other plugins available that might help; we have done something similar with GEOmyWP in the past.

matching base on zip code is something which will work. is there any documentation to follow?

Sure, so is the painting project a custom post type? And zip code for the job location is stored in post meta?

Is your automation workflow then that when a new job gets posted, you loop through users with a matching zip code value and send them an email?

There are largely 2 key concepts that might cause some confusion here: https://automatorplugin.com/knowledge-base/post-meta-tokens/ and https://automatorplugin.com/knowledge-base/user-loops/. The basic approach would have the post being published as a trigger, then you would loop through users (probably with some role or meta to identify them as vendors) and use the email action to send a communication to any of the users with a matching value for the zip code from post meta in the trigger. You can also learn more about conditions here: https://automatorplugin.com/knowledge-base/action-filters-conditions/.

There is some complexity here though and please note that the use of loops and conditions does require our Pro version.

yes the zip is stored in post meta

for example: 90210 is the post ‘customer who needs house painted’

we then need to match it with all users who are in catchment area with that post code(say 902**)

• This reply was modified 9 months, 1 week ago by hmc.

Thanks!

Right now we cannot match the first 3 characters in a straightforward way, but there are some workarounds to make this work.

Once would be to pass the data to our “Call a custom function” action, where you can call the “substr” function, then for your arguments, pass in the zip code token, then 0, then 3. The response will be returned in a token that you can use in a condition, so something like this: https://cln.sh/8KPjTctz. Still, that gets a lot harder if vendors can be linked with multiple zip codes in a single field. I guess since we’re working with the first 3 numbers only you could use a “Contains” criteria option instead; that would work.