HarborCRM Workflows
Overview
Use this skill for HarborCRM tasks that must return one JSON object only.
The template is the schema authority. The prompt supplies the task-specific rules. The API data supplies the records.
Workflow
- Read the prompt and the answer template first.
- Fetch the runner-supplied HarborCRM base URL and only the endpoints named by the prompt or required by the template.
- Load
GET /api/policiesearly so controlled enums and qualification rules stay consistent. - Build the output in the exact shape the template expects. Do not add fields or reuse example values.
- Normalize contact facts before comparing records:
- emails: trim and lowercase
- phones: strip all non-digits
- names and company names: preserve display text unless the prompt says otherwise
- Classify with the narrowest status set allowed by the template.
- Use CRM state to decide
create_*,update_existing,no_import, orsuppress. - Sort every list exactly as requested. If the prompt is silent, use the template order rules.
- Count only surviving records for totals and action counts.
- Return JSON only.
Task Families
- Event handoff: reconcile sponsor status, event leads, follow-up dates, and CRM work.
- Trade-show prospecting: qualify exhibitors, assign platform coverage, and summarize overlaps and exclusions.
- Import cleanup: dedupe rows, apply suppression, normalize contacts, and count import actions.
Reference
See references/harborcrm.md for the stable HarborCRM rules, status handling, and tie-break guidance.