- Integrations
- /
- Close
- /
- Actions
- /
- Log Activity
ActionCloseUpdated May 2026
How do I log an activity on a Close lead?
Short answer: Drop the "Close → Log Activity" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Inputs
The fields this action accepts.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Lead ID lead_id | string | Required | Lead ID. Example: lead_abc123 |
Note Content note | string | Required | Note Content. Example: Had a great call. They're interested in the enterprise plan. |
Sample request
{"lead_id": "e.g. lead_abc123","note": "e.g. Had a great call. They're interested in the enterprise plan."}
Returns
{"id": "acti_abc","note": "Had a great call.","lead_id": "lead_abc123","date_created": "2025-01-15T12:00:00Z"}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Log Activity.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Log Activity.
What does the Log Activity action do in Close?
Logs 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.
What inputs does Log Activity require?
Required: Lead ID, Note Content. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Close returns an error?
The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.
Does Log Activity support batch operations?
Yes. Run Log Activity inside a Loop node to process arrays. Tiny Command handles Close's rate limits automatically so you don't have to throttle manually.
More actions
Other Close actions.
Action
Create Lead
Creates 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.
ActionCreate Opportunity
Creates 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.
ActionCreate Task
Creates 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.
ActionDelete Lead
Hard-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.
ActionGet Lead
Returns 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.
ActionList Leads
Paginated 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.
Send log activity from your workflows.
Triggered by anything in the catalog. Free tier available. No credit card.