All articles
Integration & Analytics

Plan CRM sync and field mapping

Define object, owner, trigger, fields, and deal behaviour before connecting a CRM.

Before you start

  • Define the intended outcome, owner, permissions, and source of truth.
  • Use a small non-sensitive test.
  • Record the current configuration before changing it.
  • Confirm workspace availability in the current UI.

Steps

  1. Document CRM objects, required fields, dropdown values, and owners.
  2. Define which Signalist status triggers sync.
  3. Connect only a CRM available in the workspace.
  4. Authenticate with an approved admin and configure user mapping.
  5. Map fields and test a few controlled contacts.
  6. Verify object, owner, source, history, and deal logic in the CRM.

Safety checks

  • The correct workspace, object, view, period, or endpoint is selected.
  • Permissions, ownership, required fields, and protected data were reviewed.
  • The test result was checked in the destination or final dataset.
  • Credentials and internal evidence are not exposed.

Troubleshooting

ProblemSolution
Wrong ownerCheck Signalist sender-to-CRM owner mapping and retest with a new contact.
Field is empty or invalidCompare field type, required values, and dropdown options.
CRM is unavailableAsk support about provisioning; do not force another connection.

Frequently asked questions

Why should I test first?

A controlled test exposes mapping, permission, data, and ownership errors before broad impact.

Can I assume every workspace has this feature?

No. Use the current UI and confirmed provisioning.

What should screenshots hide?

Credentials, tokens, personal data, customer records, internal URLs, and identifiers.

Who should own the configuration?

Assign an accountable administrator and a business owner.

What should I document?

Purpose, scope, owner, fields or filters, test result, and review date.

When should I contact support?

When availability, saved state, permissions, or results remain inconsistent after a controlled check.