CFN Marketing CRM Contacts Skill

## Purpose

14 stars

Best use case

CFN Marketing CRM Contacts Skill is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

## Purpose

Teams using CFN Marketing CRM Contacts Skill should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

You only need a quick one-off answer and do not need a reusable workflow.
You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/cfn-marketing-crm-contacts/SKILL.md --create-dirs "https://raw.githubusercontent.com/masharratt/claude-flow-novice/main/.claude/cfn-extras/skills/marketing/cfn-marketing-crm-contacts/SKILL.md"

Manual Installation

Download SKILL.md from GitHub
Place it in .claude/skills/cfn-marketing-crm-contacts/SKILL.md inside your project
Restart your AI agent — it will auto-discover the skill

How CFN Marketing CRM Contacts Skill Compares

Feature / Agent	CFN Marketing CRM Contacts Skill	Standard Approach
Platform Support	Not specified	Limited / Varies
Context Awareness	High	Baseline
Installation Complexity	Unknown	N/A

Frequently Asked Questions

What does this skill do?

## Purpose

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

AI Agents for Marketing

Discover AI agents for marketing workflows, from SEO and content production to campaign research, outreach, and analytics.

SKILL.md Source

# CFN Marketing CRM Contacts Skill

## Purpose
Manage CRM contacts through n8n workflow integration. Create, update, retrieve contacts and manage contact segments.

## Operations

### 1. create-contact.sh
Create a new contact in CRM.

**Parameters:**
- `--email` (required): Contact email address
- `--first-name` (optional): First name
- `--last-name` (optional): Last name
- `--company` (optional): Company name
- `--phone` (optional): Phone number
- `--custom-fields` (optional): JSON string of custom fields

**Example:**
```bash
./operations/create-contact.sh \
  --email "john@example.com" \
  --first-name "John" \
  --last-name "Doe" \
  --company "Acme Corp" \
  --phone "+1-555-0100" \
  --custom-fields '{"industry":"Tech","size":"50-200"}'
```

### 2. update-contact.sh
Update existing contact information.

**Parameters:**
- `--contact-id` (required): Contact identifier
- `--email` (optional): Updated email address
- `--first-name` (optional): Updated first name
- `--last-name` (optional): Updated last name
- `--company` (optional): Updated company name
- `--phone` (optional): Updated phone number
- `--custom-fields` (optional): JSON string of custom fields to update

**Example:**
```bash
./operations/update-contact.sh \
  --contact-id "contact-123" \
  --company "New Company Inc" \
  --custom-fields '{"industry":"Finance"}'
```

### 3. get-contact.sh
Retrieve contact information.

**Parameters:**
- `--contact-id` (optional): Contact identifier
- `--email` (optional): Contact email (alternative to contact-id)
- `--include-history` (optional): Include interaction history (true/false)

**Example:**
```bash
./operations/get-contact.sh \
  --contact-id "contact-123" \
  --include-history true
```

### 4. add-to-segment.sh
Add contact to a segment/list.

**Parameters:**
- `--contact-id` (required): Contact identifier
- `--segment-id` (required): Segment/list identifier

**Example:**
```bash
./operations/add-to-segment.sh \
  --contact-id "contact-123" \
  --segment-id "active-customers"
```

### 5. remove-from-segment.sh
Remove contact from a segment/list.

**Parameters:**
- `--contact-id` (required): Contact identifier
- `--segment-id` (required): Segment/list identifier

**Example:**
```bash
./operations/remove-from-segment.sh \
  --contact-id "contact-123" \
  --segment-id "inactive-leads"
```

## N8N Integration

All operations invoke n8n workflows via HTTP POST to endpoints configured in `.env`:
- `N8N_BASE_URL`: Base URL for n8n instance
- `N8N_API_KEY`: Authentication key

## Error Handling

Scripts return:
- Exit code 0: Success
- Exit code 1: Parameter validation error
- Exit code 2: Network/API error
- Exit code 3: Authentication error

## Response Format

All operations return JSON with structure:
```json
{
  "success": true,
  "data": { ... },
  "message": "Operation completed successfully"
}
```

Related Skills

We are still matching the closest adjacent skills for this page. In the meantime, continue through the full directory.