Salesflare

Salesflare

Salesflare is a CRM that automates data entry from email/calendar. Manage accounts, contacts, opportunities, and tasks.

Data Model

• Accounts — companies; the anchor entity. Create accounts before contacts or opportunities.
• Contacts — people tied to accounts via account ID. Always find or create the account first.
• Opportunities — pipeline deals with value, stage, and close date. Require an account ID.
• Tasks — to-do items optionally linked to accounts. Have description, reminder_date, completed status.
• Tags — labels applied to accounts, contacts, or opportunities. Auto-created when passed in upsert calls.
• Pipelines — sales process stages. Read-only via API. Each pipeline has a stages array with IDs needed for opportunity stage assignment.
• Workflows — automated email sequences. Read-only listing.
• Internal notes — free-text notes attached to an account, visible in the activity feed.
• Custom fields — workspace-specific schema extensions for accounts, contacts, or opportunities.

Key Relationships

• Contacts → Account (via account field)
• Opportunities → Account (via account field, required)
• Opportunities → Stage (via stage ID from pipeline)
• Tasks → Account (via account field, optional)
• Notes → Account (via account field, required)

Workflow

1. List pipelines to get stage IDs for opportunities
2. Create or find accounts first (companies)
3. Add contacts linked to accounts
4. Create opportunities on accounts with appropriate stage
5. Add tasks for follow-ups
6. Use notes for call/meeting summaries

Gotchas

• Contacts API expects an array body on create (single object returns single object)
• Tasks API expects an array body on create
• Tags are strings — pass ["tag1", "tag2"] in upsert calls; they auto-create if new
• Opportunity creation requires account ID
• Stage IDs come from the pipeline's stages array, not a separate endpoint