Start with the question
CRM data mixes company records, personal information and actions that can change a customer relationship. Define a narrow read task first, such as summarizing a test company record. Do not begin a connector evaluation by granting broad write access.
A workflow you can check
Use the following steps as a small acceptance test. Keep the underlying observations with your notes so someone else can review the conclusion.
- Verify the connector operator and setup instructions with the CRM provider.
- Select the smallest account and data scope needed for the test.
- Inspect available tools for record writes, exports and communication actions.
- Compare a returned test record with the CRM interface and document revocation.
Interpret the evidence
MARqentic is not a HubSpot CRM connector. Keep CRM actions in the separately authorized integration and label the source of any joined data. A company research result and an internal CRM record have different ownership, freshness and access requirements.
A prompt to adapt
Replace the inputs with your own approved examples. Ask the assistant to explain its scope before starting research.
Write a HubSpot connector acceptance test that reads a known test company, checks field provenance and identifies permissions that are unnecessary for that task.