Add context to workflow automation (Make automation even smarter & more powerful)
Here is the scenario:
Whenever our sales reps add new companies or contacts to Salesmate.io we created a automation that automatically assigns ownership to their Sales Manager. We refer to this as "The House" account (like a casino).
A sales rep doesn't actually "own" a company or contact until they are able to win a deal with them. If they win a deal, then we change ownership of company & contact over to the sales rep and therefore no other sale rep can reach out to this account because it belongs to another rep.
The automation we want is to be able to update Company and Contact associated with a deal that is won. Currently we can do that, however, the automation is lacking CONTEXT. When creating a new automation using the deal module / object it allows us to update the company owner field, however, it asks us to simply pick a user.
What is SHOULD be able to do, is let us pick "the current deal owner" as a user in the dropdown control. This would make it contextual to the deal being processed by the automation. Much like you already use context in filters such as "currently logged in user" or "you" in dashboards etc.
I know this a nuanced request. But I think its a very powerful addition to automations. Being able to reference the data of current object being processed by the automation will open up many new possibilities.
-
So, my workaround for now was to use the same logic shown here https://support.salesmate.io/hc/en-us/articles/115002604732-How-to-Automatically-Create-a-Deal-in-a-Pipeline-once-a-Contact-is-created-or-Updated-with-a-Tag-or-a-Field-using-Workflows
I created an automation that will update the company owner based on the deal owner whenever a deal is won. Unfortunately, I discovered that when placing a webhook call to update the company using PUT and https://apis.salesmate.io/v1/companies/{{Company.id}} the automation is NOT ABLE to use the {{Company.id}} variable in the URL
So, my request for now is to at least have the webook URL call be able to handle dynamic variables. This would allow me to achieve some level of "contextual" behavior as described in my original feature suggestion above.
Please sign in to leave a comment.
Comments
2 comments