Michael Clark replied 2 years ago

Yeah, from the docs, it's not clear that form action automation won't work out-of-the-box. There's a *suggestion* that converting to native server cron is a way to ensure consistency, but if that's a requirement, that should be in the doc. Also, does disabling wp cron in wpconfig mean that form action automations are now default native crons or does a cron need to be created manually for each form action automation (thereby eliminating the "automation" part?). Not trying to be contrarian, and totally not hating on Formidable, because I love it. Just seeking some clarity on which way to go. Because If I have to create a native cron for each form entry, I'll have to set up a Zap or n8n workflow to do it automatically. Just need to know which way to go. Setting up an API in my server to map and make cron jobs is gonna require me to alter my release date a bit. Also adds a layer of complexity i was hoping to avoid. xP

Bobby Clapp replied 2 years ago

I don't disagree. I would create a cron job against wp-cron.php as that is kind of the house for everything that does automation. Hopefully that will do it for you.

Michael Clark replied 2 years ago

Yep. I'm probably going to offload this to a cron service and use the Formidable API plugin to help automate it. The issue with this is I think that no matter which automation service I use, I'm going to have to have a meta workflow where it clones itself and then saves as a new version based on the parameters passed. It'll be fun, and mind numbingly fiddly. Especially with Zapier.: Form -> Webhook -> Zapier Scheduler -> Sendgrid or Twilio or both. That Zap can't just be run on the schedule, it has to be cloned to run for each form entry. Dunno if that's even possible.^^!

Michael Clark replied 2 years ago

Actually, no can do with Zapier. Gotta make one with some other workflow automator.