A data source connects an external or website event to the selected workspace. Verify the destination, authorization, field mapping, and test result before making the source active.
The names of buttons and sections can vary with your PloverCRM plan, permissions, connected services, and current version. When a label differs, use the matching label displayed in your account and do not change an unrelated setting.
Safe troubleshooting order. Confirm the correct account, workspace, connected website, browser, and user role. Record the exact non-sensitive error, affected screen, approximate time, and last successful step. Check the relevant status page or log before changing configuration. Make one low-risk correction at a time and wait for the result. Verify the result before retrying or escalating. Do not delete records, reinstall plugins, reconnect integrations, or rerun imports merely because a page looks stale; these actions can change data or create duplicates.
Steps #
- Open Data Sources and Imports and choose the source or connection type.
- Confirm the selected workspace and review any existing connection with the same purpose.
- Enter only the required configuration values or continue through the approved authorization screen.
- Set the destination, routing, lists, tags, and field mapping where those controls are available.
- Run the connection test or send a safe test event.
- Review the test result and source log for accepted, rejected, or unmapped data.
- Save the configuration and enable the source only after the result is understood.
- Monitor the first real event and confirm that it reached the intended lead or queue.
What to verify #
After the final step, confirm:
- The workspace name and connected website still match the intended destination.
- The status, record, filter, setting, or result reflects the change you made.
- No unrelated lead, teammate, connection, message, or automation was changed.
- Any export, notification, file, or external action follows your organization’s privacy and retention policy.
PloverCRM should display a confirmation, updated status, or refreshed record. If the workflow is asynchronous, use its progress or log view instead of submitting the same request again.
Troubleshooting #
- If the screen or control is missing, confirm the workspace and ask an administrator to review your role.
- If results are empty or stale, clear filters, refresh once, and check workspace connection status.
- If a value is rejected, read the field-level message and use the required format.
- If an operation is processing, wait for its status or log entry before trying again.
- If the result is unexpected, stop before making another change and record the exact non-sensitive message, approximate time, browser, and reproduction steps.
