The playbook
CRM Integrations: Template and Field Guide
This CRM integrations template turns a broad task into a record another person can use. It captures source, target, field, then connects that information to a decision. Copy the table into your working document or system and create a separate record for each item in scope.
Put the task in context
Decide which application owns each shared field, then map IDs and update direction. A contact's email changing should not automatically create an unrelated new person. Test retry behavior and reconcile records after temporary connection failures.
Copyable worksheet
| Field | Entry instructions |
|---|---|
| source | Record the source associated with this customer or opportunity record. Use a stable reference so later updates can be matched. |
| target | Record the target associated with this customer or opportunity record. Keep the value specific enough for another owner to interpret. |
| field | Record the field associated with this customer or opportunity record. Keep the value specific enough for another owner to interpret. |
| owner | Record the owner associated with this customer or opportunity record. Keep the value specific enough for another owner to interpret. |
| sync rule | Record the sync rule associated with this customer or opportunity record. Keep the value specific enough for another owner to interpret. |
| Decision field | Entry instructions |
|---|---|
| Observed problem | Describe the actual condition and where it was observed. |
| Recommended action | State the smallest action that resolves the documented problem. |
| Evidence | Link to the record, observation, or test supporting the action. |
| Owner and next review | Name the accountable person and when the decision should be revisited. |
How to complete the worksheet
Begin with source. Use the same reference throughout the record so notes are not attached to the wrong item. Then map objects identifiers and field direction. This establishes the information required before the worksheet becomes a request for action.
Next, decide which system owns each shared value. Use the observed problem and evidence fields to explain why that step is needed. A useful entry describes an actual condition, such as allowing both systems to overwrite the same field without rules, rather than a broad instruction to “improve performance.”
Finally, test failures retries and duplicate creation. Put establish field ownership and conflict handling in the action field only when it addresses the observed condition. If the problem is different, change the action. The template is a structure for judgment, not a reason to apply the same fix everywhere.
Illustrative completed decision
| Part | Illustrative entry |
|---|---|
| Problem | Allowing both systems to overwrite the same field without rules |
| Action | Establish field ownership and conflict handling |
| First check | Map objects identifiers and field direction |
| Follow-up check | Test failures retries and duplicate creation |
| Outcome to define | reconciled synchronized records |
Adapt the fields without losing meaning
You can add fields required by your team, but each should change a decision or preserve necessary context. Keep factual observations separate from recommendations. If target changes, record the new value and its effective date instead of silently rewriting the context of an earlier decision.
Use the record in a handoff
Ask the receiving owner to explain the next action using only the worksheet. Missing context becomes visible quickly during that exercise. Repair the record before applying the structure to a larger batch. Keep reconciled synchronized records connected to the item so the team can later assess whether the action was useful.
Preserve the context of the last meaningful conversation. The next owner should know what was promised, what remains unresolved, and who is expected to act. A stage label alone rarely supplies enough information.
Skip the manual steps. Let AgentixCRM run this for every client.
Start now