Menu

Individual skill

harbor-crm-integration

0upvotes

Integrate HarborCRM REST API data for post-event reconciliation, trade-show exhibitor prospecting, contact import batch preparation, campaign member management, and cross-entity CRM workflows. Use whenever a task mentions HarborCRM, event reconciliation, trade-show lead qualification, contact import cleaning, sponsor finance handoff, CRM data merge, badge-based lead handoff, or any multi-entity data integration against the HarborCRM API — even if the user doesn't name it directly.

experiments/codex_skill_creator_comparison_deepseek_v4_pro_max/reports/skills/task_group_001/fewshot/opencode/fewshot_attempt_01/SKILL.md

Read pinned source

Source commit 5082a777379156a048881e94940d640702e5e09a

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
121
Repository last updated
Oct 29, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# HarborCRM Integration

Work with the HarborCRM REST API to fetch, cross-reference, classify, and produce structured JSON output across events, finance, CRM, trade-shows, and import pipelines.

## How to approach any HarborCRM task

1. **Read the answer template** the task provides. It defines every required key, allowed enum value, sort order, and field type. The template is the authoritative schema for the output.

2. **Fetch `/api/policies` first.** Policies carry the business rules that drive qualification, opportunity sizing, follow-up offsets, source priorities, and controlled vocabulary. Everything else follows from them.

3. **Pull all relevant API data in parallel.** The API has no dependencies between endpoints — fetch event+orders+badges+sponsor_packages together, or tradeshow+exhibitors+meeting_interest together. Then fetch invoices, CRM entities, and campaign members in a second wave once you know which IDs to filter by.

4. **Match entities by ID first, then by normalized email, then by normalized company name.** See [references/data-model.md](references/data-model.md) for the exact join keys between entities.
Back to top