It sounds like you’d be able to trigger an event from the JO and have the event trigger a real time rule.

• Create an event to accept the data you need for the rule
• Create the API call in JO and call the event you created. Make sure you have all of the data you’ll need for the API call in the participants config.
• Create a real time rule based on the event being triggered.

You might be able to incorporate the same event to send a completed status once the JO has finished. Depending on how it’s all structured.

Ah thank you. 

We log the emails in the customer’s timeline - so do you think I can build a rule that notices the timeline activity and then updates that field?

You could do it that way as well, but you’d be more dependent on the rule schedule. Maybe not a problem for your use case, and team. The benefit of triggering an event is that it would trigger the change to the company field quicker. It’s a bit more complicated than just reading timeline though.

Should be fine to do this in line with our rule schedule, due to the nuances in the way we are already set up. What do you recommend the best identifier is to pick up on the timeline activity? Subject line? I need to make sure we identify the first email within that specific journey, not any time anything is logged to timeline. that would be messy!

If you’re going to go that route, I’d look into using the email logs rather than timeline. They’d have a reference to the actual JO or template.

Thank you!