Custom Field Mapping

EspoCRM lets an organization define its own fields and entities on top of the standard contact and deal records, which means the exact data a Beam agent reads and writes varies by account. A Beam agent is configured against the specific fields a customer has set up, such as a custom stage or a tagged attribute, and applies the approved rule for updating them when a trigger event occurs. It writes the update back to the correct custom field rather than a generic note. A field it doesn't recognize, or a value outside the expected set, gets routed to a person to correct.

Pipeline Stage Updates

Deals in EspoCRM move through a defined pipeline of stages from open to won or lost. A Beam agent reads a deal's current stage alongside the event that should move it forward, such as a signed contract or a completed call, and applies the approved rule for advancing the stage. It updates the deal record and adds a note explaining why the stage changed. A deal that meets more than one rule at once, or one with no matching trigger, gets routed to a person to move manually.

Contact Record Sync

EspoCRM holds the core contact record that other tools in a stack often need to match against, such as an email platform or a support desk. A Beam agent compares a contact's details in EspoCRM with the same contact elsewhere, applies the approved rule for which fields take priority, and updates the record so the two stay aligned. It notes when a change came from an external source rather than a person editing EspoCRM directly. Conflicting values between systems, where the rule doesn't clearly say which wins, get routed to a person to settle.