Tyron_Pretorius

@Pavel_Plachky your use case of sending confirmation SMS messages to customers and handling responses is something I have built in Marketo and Zapier: https://theworkflowpro.com/marketo-sms-integration/https://theworkflowpro.com/2-way-sms-marketo/The first post shows you how to use webhooks to send ...

@Trevor_Sparks I actually built out this exact workflow in Zapier! https://theworkflowpro.com/2-way-sms-marketo/ In the post above, I show how to:Parse the inbound message for the "STOP" or "START" keywordUse the Marketo REST API to lookup the lead's email based on their phone numberUse the lead's e...

Nice post Sanford! I just wanted to let people know that there is another option to do number lookup in Marketo using webhooks. As I share in this forum post, you can call the Telnyx number lookup API (which is free compared to Twilio's paid lookup) using a webhook and map the response attributes to...

Just to provide people with another vendor option for SMS I recently published a blog on the Marketo forum that shows how to use webhooks to integrate with the Telnyx SMS API: https://theworkflowpro.com/marketo-text-messaging/ @Victor_Herrero I saw your later comments about wanting to do number lo...

Thanks Sanford!

Hey Sanford, Yes, there is an SFDC sync step in the "02a MQL Request with Routing campaign". So would you say this is expected behavior? It seems odd to me because SFDC is changing these fields as opposed to a flow action within the campaign, which is what this insinuated to me initially