Skip to content
CRM & SalesReal-timeUpdated May 2026

Close

Sales-call-focused CRM Close, scripted

Close is the CRM built for inside sales teams that live on the phone, power dialer, call recording, and SMS/email logging as the primary interaction primitives, not bolt-ons. Nine actions cover the lead and activity surface: Create Lead, Get Lead, Search Leads, List Leads, Delete Lead, Create Opportunity, Create Task, Log Activity (the key one for call logging from external dialers), and List Leads filtering by status or owner. No triggers today (Close's webhook system is set up per-event in their UI; native triggers are on the roadmap). The integration uses a Close API key from your team settings. Close's Lead object is the unit (rather than Contact + Account as separate things), with all the contacts, opportunities, calls, and emails associated to a single Lead, actions reflect that. Common pattern: an Aircall call ends and Log Activity records the call on the matching Close Lead (with duration, recording URL, and rep), or a Calendly demo booking creates the Close Lead with the form answers as custom fields so the rep walks into the call already prepared.

0triggers
9actions
≈ 2 minto set up
Freetier · no card
Actions

Do anything Close can do, from a workflow.

Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.

ActionWhat it does
Create LeadCreates a new lead (company-level record) in Close CRM with contacts, addresses, custom fields. Close's lead-first model means each company is one lead, with multiple contacts nested. The standard hook for "B2B form submission → push to Close" sync workflows.
Create OpportunityCreates a sales opportunity tied to a lead with value, expected close date, status, pipeline. Useful for "auto-create opportunity when lead reaches qualification score" workflows.
Create TaskCreates a follow-up task for a sales rep tied to a lead with due date and notes. Useful for "deal stagnant for N days → create follow-up task for the AE" hygiene automation.
Delete LeadHard-deletes a lead and all associated contacts, activities, opportunities. Irreversible. For GDPR right-to-erasure compliance workflows; for soft removal that preserves activity history, change the lead status to "Archived" instead.
Get LeadReturns a lead by ID with contacts, custom fields, opportunities, and recent activities. The standard lookup for enrichment workflows or for round-trip operations that need the current lead state.
List LeadsPaginated leads with filters by status, custom fields, recently updated. For sync workflows that mirror Close into a warehouse or BI dashboard, paginate with the date_updated filter for incremental pulls.
Log ActivityLogs a custom activity (call, email, note, meeting) on a lead's timeline. Useful for "AI-summarised post-call notes from Gong/Fireflies → log on the matching Close lead" workflows that keep the rep's history complete.
Search LeadsSearch by Close's query language (status:active company:"Acme" etc.). Returns matching leads with relevance ranking. The standard "find before update" pattern and the workhorse for ad-hoc rep lookups.
Update LeadPartial update on lead fields — only passed fields change. For "Apollo enriched this lead → write back to Close" augmentation patterns and for "stage change in external system → reflect in Close" sync workflows.
Recipes

Pre-built Close workflows.

Clone any recipe and customize it in one click. Every recipe is fully editable.

Before you build

Three things worth knowing.

Filter at the trigger

Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.

Authorize once, reuse anywhere

Connect Close once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.

No JSON to read

Every Close field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.

FAQ

Questions about the Close integration.

If we missed yours, ping support. We usually reply within an hour.

How do I connect Close to Tiny Command?
Open the Tiny Command workflow builder, drop in a Close node, and click Connect. Authorize Close once and any workflow on your account can use its triggers and actions. Most teams finish the connection in under two minutes.
What Close triggers does Tiny Command support?
Tiny Command focuses on outbound actions for Close today. Use Tiny Command's universal Webhook or Schedule trigger to start Close workflows, then run any Close action you need.
What Close actions can I run from a workflow?
9 Close actions are available out of the box, covering crm & sales operations like "Create Lead". Every action accepts dynamic inputs from upstream nodes, whether that's a search result, an AI output, or a form field.
Is the Close integration real-time?
Close actions execute synchronously inside your workflow. Tiny Command waits for Close's API to confirm before continuing to the next step, so downstream nodes can rely on the result.
Do I need to write code to use Close with Tiny Command?
No. Every Close trigger and action is fully configurable from the visual workflow builder. For edge cases that aren't covered, drop in a custom HTTP node and call any Close API endpoint directly.
How much does the Close integration cost?
There's a free tier you can start on without a credit card. Higher run volumes and team features come with paid plans. The Close integration itself has no per-app surcharge.
Related

More crm & sales apps people connect.

Same category as Close, ordered by how often teams pair them. Hover the carousel to pause.

Do more with Close.

Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.