-
-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for CRM integrations and developer guidance #19
Comments
These are all on the list, roughly planned out via the Roadmap. No ETA, but we're prioritising them in stages, as we know how important these sorts of things are. When you say API developer documentation, are you referring to just the integrations stated above, or general Formie developers docs? |
@engram-design I should have looked before I spoke - the developer docs look great already! As long as the CRM integrations are documented as thoroughly as everything else, I'm happy. It's also really important that these CRM integrations have clear, unchanging APIs. Pretty much every project we do at Venveo ultimately has some CRM customization, such as completely new integrations, working with things like tags, lists, workflows, and modifying field values before being sent. |
Great, would just like to add following integrations from Freeform as well:
|
Glad to say this is now implemented in 1.2.0, providing support for 36 new integrations. Email Marketing
CRM
Webhooks
Miscellaneous
Check out the developer docs if you're interested in creating your own providers, and make sure to dive into the core integration PHP classes. Any further integrations you're after - start a new issue and we can track from there. |
Description
This plugin is gorgeous and I would love to use it! Unfortunately, we're unable to use it for literally any of our clients until we have support for common CRM integrations and API developer documentation. These are a few integrations we use regularly that are all supported by Freeform:
Additional info
The text was updated successfully, but these errors were encountered: