Multiple workflows, only the first one triggered is working

  • 1
  • Problem
  • Updated 2 years ago
  • Not a Problem
Hoping you can help with a perplexing problem. One of our subaccounts has several active workflows set up: each of these sends an immediate email, and then sends a second email a day later. The workflows are set up using "signs up to receive your emails" and the "all" option is selected; the target audience for the workflow is a specific group that people are added to when they complete a signup form. The complicating factor here is that our client is using a plugin, ConvertPlug, which creates the signup forms. So we're unable to select a specific signup form as the trigger, so we've selected the specific signup group that the ConvertPlug plugin adds people to. I understand that this plugin is not supported by Emma, but I hope you can answer the Emma-related questions that surround it. 

But these workflows only work the first time you trigger one of them. (In other words, I fill out form #1, and then also fill out form #2. I get the automated email for form #1 but I never get the automated email for form #2). My guess at what's happening here is that subsequent signup form click isn't being treated as a "signs up to receive your emails" trigger. Is that a correct reading of the situation? 

Given the limitation that we can't set up a workflow that's based on a specific signup form (because of the plugin involved), can you suggest a workaround that will allow subsequent signup form clicks to trigger automated emails? 
Photo of Meaghan

Meaghan, Champion

  • 83 Posts
  • 15 Reply Likes

Posted 2 years ago

  • 1
Photo of Sam Collis

Sam Collis, Customer Support Specialist

  • 252 Posts
  • 59 Reply Likes
Hi Meaghan!

It sounds like ConvertPlug might be using the /members/add call to add contacts to your client's audience.  This is method is only able to execute the email signup trigger for the first time a contact is added into the account, which is why on the second instance that 'signup' isn't entering the workflow.

If you're able to have any say in the method used to add those contacts via the API, then it should work if instead you're able to use the members/signup/[signup form id] call as this is basically imitates the use of a classic form, and so should work the same way as if an audience member signed up using one of our forms allowing a contact within the account to execute a signup trigger. The signup form ID can be grabbed from an existing classic form by using the "add this to my site" button.

If this isn't possible then the second-best option is to look at using a field change trigger.  If there is generally an order that one might use the forms, then it's fairly straight forward to have the second form use a field change trigger and include a new field that's required (this will ensure that something is changed on the contact record to trigger the workflow).

If there isn't a particular order then it get's a little more tricky.  You could potentially have 2 workflows setup for each form, as a normal signup trigger and another using the field change.  That way, for example if a contact uses form #2 to be added to the account, then they'd be added to the workflow using the signup trigger.  If that same contact used form #1 later, they would be able to be added to the workflow that uses the field change trigger.  And vice versa. Keep in mind that this does assume that some sort of information change is going to occur on the second form being filled out.  One option might be a really simple field specific to each form/workflow.

Lastly, our Technical Services team would probably be able to spin something up to enable the integration work a little more friendly with Emma.  If that's a path you'd like to explore please just let me know.

Please don't hesitate to ask me any follow-up questions!
Photo of Meaghan

Meaghan, Champion

  • 83 Posts
  • 15 Reply Likes
Sam, thank you so much for this thorough reply. Your explanation about the plugin's API call is super helpful, and something I never would have come up with on my own. Thanks for putting some thought into possible work arounds. I'll put my head together with the client and we'll be back if we have additional questions (or more insights to share with the community). Thanks again!