Tools for Sugar CRM

Expand the SugarCRM connector so Jenius can support the same level of functionality that is available with our Salesforce integration.

Specifically, we need:

Full read and write access to Accounts and Opportunities.
Access to the relationship between Accounts and Opportunities.
Access to all standard Opportunity fields, including (but not limited to):
Opportunity name
Account name
Stage
Amount / Deal Size
Probability
Open/Created Date
Close Date
Owner
Next Steps
Description
Status
Read and write access to all custom fields on Opportunities.
Read and write access to custom modules/objects that are related to Opportunities.
The ability to retrieve both the schema (available fields) and the data so Jenius can dynamically work with customer-specific customizations.
Support for creating and updating records where permitted by SugarCRM permissions.

We also need event-driven triggers so Jenius workflows can be initiated automatically when changes occur in SugarCRM, for example:

Opportunity created
Opportunity updated
Opportunity stage changed
Account created or updated
New activity, task, meeting, or event created
Any configurable change to a standard or custom object

The goal is to provide feature parity with our Salesforce integration, allowing Jenius to securely read CRM data for AI workflows and write updates back to SugarCRM, while also supporting trigger-based automations when CRM data changes.

Start by comparing the existing Salesforce integration with SugarCRM's API capabilities, especially records, custom modules, schemas, relationships, permissions, and event triggers. Confirm the scope and available entry points before implementation. Done means the requested read/write operations, dynamic fields, and configured change triggers work securely and have coverage for the listed CRM scenarios.

Written by the indexing model from the issue text.