# Platform Connection Checklist

Use this reference after onboarding identifies the agent's stack.

## Website/CMS discovery

Record:
- Platform and current version or plan, when relevant.
- Blog collection and template.
- Draft, preview, and publish capabilities.
- Native form blocks and embed restrictions.
- SEO fields, schema support, canonical behavior, and redirect tools.
- Media library requirements.
- Available official API or connector.
- Authentication method and least-privilege scope.

## CRM discovery

Record:
- CRM and account/workspace.
- Native form or inbound lead endpoint.
- Required contact fields.
- Source, campaign, stage, tags, assignment, and consent fields.
- Duplicate-contact behavior.
- Automation triggers and whether activation is approved.
- Test-contact cleanup policy.

## End-to-end proof

For an authorized test:
1. Use an obvious test identity and non-production message.
2. Submit through the exact live or staged website form.
3. Confirm success state in the browser.
4. Find the resulting CRM record.
5. Verify source, campaign, tag, stage, community interest, and assignee.
6. Verify consent fields were stored accurately.
7. Confirm no unapproved message or automation fired.
8. Remove or clearly label the test record according to the user's policy.
9. Save screenshots or structured proof without exposing personal data.

## Common fallback patterns

- Website native form to official CRM integration.
- CRM hosted form embedded in a website block.
- Supported automation connector with documented field mapping.
- Scoped webhook/API endpoint.
- Manual CSV import with a repeatable mapping.

Never paste secrets into a blog editor, public HTML, source log, screenshot, or deliverable.