People have already been integrating filemaker with IoT style services (if this then that, and zapier as well). Writing to filemaker with webhook methods and commanding from filemaker using Insert From URL and the like.
The issue with setting up an FM specific Zap is that the structure for each database's Data API is dynamically generated based on table names and such, and Zap prefers known endpoints that don't change. So if you do set one up, it would require some amount of consistency on the filemaker side for it to function properly.
I understand - but plenty of other services on Zapier are based on dynamic content like survey questions for JotForm. Perhaps this is something that FileMaker needs to address themselves. If I were attending DevCon, I'd love to raise the question with Product Management.
For it to go in directly as a filemaker branded thing, you are correct in that most likely FMI themselves would need to set it up with Zapier directly.
This should go into Product Ideas then: https://community.filemaker.com/community/discussions/product-ideas
As for setting up your own and doing it custom, I think the issue isn’t with variable URL parameters, but rather the need for zapier to have a specific URL for your endpoint. EG if you check their documentation under https://zapier.com/developer/documentation/v2/reference/#app-summary “action endpoint url”, the only dynamic parameters are for auth and parameters; but the URL itself is static. Unless you can make the destination URL itself completely variable, then I’m not sure how you would set it up aside from using the existing Zap for pointing to webhooks.
If you do pursue developing your own, please share it here with the community!