- Issue created by @camoa
- π©πͺGermany jurgenhaas Gottmadingen
This sounds amazing. As an ECA maintainer I'd be happy to provide help when needed.
I have a client who uses Salesforce extensively, and we see the potential to create custom automations between their Drupal site and Salesforce CRM using the ECA module.
Currently, several integrations require custom module development for anything beyond basic field mapping, which increases development and maintenance costs.
The ECA (Event, Condition, Action) module provides a powerful no-code solution for workflow automation within Drupal, but it doesn't currently connect with Salesforce events or actions. An integration between these systems would allow site builders to create sophisticated Salesforce integrations through configuration instead of custom code.
Not applicable for a feature request.
Create a `salesforce_eca` submodule for the Salesforce Suite that potentially could:
1. Expose Salesforce events to ECA (object creation, field updates, deletions, etc.)
2. Provide ECA conditions for evaluating Salesforce data (field values, record existence)
3. Implement ECA actions for triggering Salesforce operations (create/update records, execute API calls)
This would enable users to build complex integrations between Drupal and Salesforce using ECA's configuration interface rather than writing custom code. Expanding the reach of the salesforce integration.
- Assess community interest in this integration
- Document common use cases
- Identify specific events, conditions, and actions to implement in the initial version
- Determine technical approach for integration with Salesforce APIs
- Design plugin architecture for extensibility
- Develop initial implementation
No direct UI changes to existing interfaces. The module would:
- Add new events to the ECA event selection
- Add new conditions related to Salesforce data
- Add new actions for Salesforce operations
All would be integrated into the existing ECA interface.
This module would leverage existing Salesforce Suite and ECA APIs.
None anticipated for the initial implementation. The module would use the existing data structures of both the Salesforce Suite and ECA modules.
Active
5.1
salesforce.module
This sounds amazing. As an ECA maintainer I'd be happy to provide help when needed.