Notifying leads with a role in an Opportunity?

[Anonymous]

Marketo has API support for creating Opportunities and associated Roles. I would like to set up a smart campaign that triggers on a stage change for the Opportunity (so far this is simple) and then has a flow that notifies someone with a given Role in that opportunity (already raised with Marketo support and told that there is no known way and suggested I post here).

I am able to add custom fields to the Opportunity object (via Marketo support request), one for each role in an Opportunity, and I can populate those with email addresses, and though clunky and redundant, I can convey the information INTO Marketo.

But having added those custom fields, am I correct that they would be inert and unusable? Because I cannot refer to them via tokens like I can for a Lead object, I still see no way to refer to these fields given a trigger on an Opportunity change.

I purely want to notify the right people when a deal enters a given stage, and I am willing to do custom coding versus various REST APIs to get there.

Has anyone found a way to do this?

[SanfordWhiteman]

You can do this using FlowBoost + Floxy.  But if even I am wary of recommending it, that might be a sign of something! Let me ask this instead: how are you updating the Opportunity records, and why can't you pair this with a Request Campaign call for the related leads? (Of course acknowledging that using more API calls isn't so hot.)

[Anonymous]

Sanford, that sounds like a promising direction, thank you for taking time to respond. We have coding talent here and are bridging Pipedrive to Marketo via the API. So far we only have a simple contact -> lead sync, but we're trying to evolve this to bring deals into opportunity objects, if we can figure out how to do gainful things with that.

If you have time to elaborate, I am unsure how exactly request campaign solves this. Since I cannot react to changes in an opportunity on a per role basis, would i somehow push all related leads into a campaign and then somehow sort them apart afterward?

[SanfordWhiteman · Accepted solution]

Request Campaign works lead-by-lead: you can think of it as a meta-trigger.  When there's no organic trigger to run a flow in the context of a certain lead, you can just say, "Okay, run this flow now."

The Campaign is Requested trigger is kind of like "Is triggered for reasons you don't need to know.."

You wouldn't be "reacting" to the changes on the server, though. What I'm describing is determining that you just made an interesting change to an Opportunity based on information in your client app.  Then kick off Request Campaign against the leads with roles in the Opportunity. If you don't have the ability to know that an interesting change is occurring, this wouldn't work.

[Anonymous]

Excellent, I will revisit this thread after we work through this and let you know how we do. Thanks again for your thoughtful replies!