Actions83
- Lead Actions
- Lead Status Actions
- Contact Actions
- Opportunity Actions
- Opportunity Status Actions
- Task Actions
- Note Actions
- Call Actions
- Email Actions
- Meeting Actions
- SMS Actions
- Custom Activity Actions
- Sequence (Automation & Bulk Actions) Actions
- Bulk Action (Automation & Bulk Actions) Actions
- Export (Automation & Bulk Actions) Actions
- Field Enrichment (Automation & Bulk Actions) Actions
Call → Create
AI-generatedOverview
This node operation creates a call activity associated with a specific lead in the Close CRM system. It allows users to log call details such as direction (inbound or outbound), duration, notes (in HTML or plain text), phone number called, recording URL, call status, date created, and the user to attribute the call to. This is useful for tracking communication activities with leads, ensuring all call interactions are recorded and accessible within the CRM.
Use Case Examples
- Logging an outbound call made to a lead with notes and call duration.
- Recording an inbound call with a link to the call recording and associating it with a specific user in the CRM.
Properties
| Name | Meaning |
|---|---|
| Lead ID | The ID of the lead to create the call for, required to associate the call with the correct lead. |
| Additional Fields | Optional fields to provide more details about the call such as direction, duration, date created, user, notes, phone number, recording URL, and status. |
Output
JSON
id- The unique identifier of the created call activity.lead_id- The ID of the lead associated with the call.direction- The direction of the call (inbound or outbound).duration- Duration of the call in seconds.note_html- Rich-text note about the call in HTML format.note- Plain text note about the call.phone- Phone number that was called.recording_url- URL to the MP3 recording of the call.status- Status of the call.date_created- The date and time when the call activity happened.user_id- The user ID to whom the call is attributed.
Dependencies
- Close CRM API key credential
Troubleshooting
- Ensure the Lead ID is provided and valid; missing or incorrect Lead ID will cause errors.
- The Recording URL must be HTTPS; non-HTTPS URLs will be rejected.
- If notes are provided in HTML format, ensure they are valid HTML to avoid formatting issues.
- API authentication errors may occur if the Close CRM API key credential is missing or invalid.
Links
- Close CRM API - Calls - Official API documentation for managing call activities in Close CRM.