Actions79
- Lead Status Actions
- Pipeline Actions
- Template Actions
- Lead Actions
- Contact Actions
- Activity Actions
- Meeting Search Actions
- Opportunity Actions
- Opportunity Status Actions
- Integration Link Actions
- Smart View Actions
- Comment Actions
- Email Template Actions
- Task Actions
- User Actions
- Custom Field Actions
Overview
This node integrates with Close.com CRM to create various types of activities associated with leads. It supports creating calls, emails, meetings, notes, and SMS activities linked to a specific lead. This is useful for automating the logging and tracking of communications and interactions with leads in your sales process.
Common scenarios include:
- Logging a phone call made to a lead, including call duration and direction.
- Sending or scheduling an email to a lead, optionally using templates and specifying CC/BCC.
- Scheduling meetings with leads, including attendees and location details.
- Adding notes (plain text or HTML formatted) related to a lead.
- Sending SMS messages to leads with optional templates.
Practical example: Automatically log an outbound call activity after a call is completed, including notes about the conversation and call duration.
Properties
| Name | Meaning |
|---|---|
| Activity Type | The type of activity to create. Options: Call, Email, Meeting, Note, SMS. |
| Lead ID | The unique identifier of the lead this activity belongs to. |
| Direction | The direction of the communication (Inbound or Outbound). Required for Call, Email, and SMS activities. |
| Phone | Phone number involved in the call (for Call activities). |
| Use HTML | Whether to use HTML formatting for note content (for Note activities). |
| Note | Plain text note content (for Call and Note activities without HTML). Also used as call notes. |
| Note HTML | HTML formatted note content (for Note activities when Use HTML is true). |
| Duration (seconds) | Duration of the call in seconds (for Call activities). |
| Subject | Subject of the email (for Email activities). |
| To | Recipient email addresses (comma separated) for Email; recipient phone number for SMS. |
| Body Text | Plain text body of the email (for Email activities). |
| Body HTML | HTML body of the email (for Email activities). |
| Email Status | Status of the email: Send Now, Schedule for Later, Save as Draft, Log as Sent, Log as Received (for Email activities). |
| Scheduled Date | When to send the scheduled email (required if Email Status is "Schedule for Later"). |
| Title | Title of the meeting (for Meeting activities). |
| Starts At | Start date/time of the meeting (for Meeting activities). |
| Ends At | End date/time of the meeting (for Meeting activities). |
| Location | Location of the meeting (optional additional field for Meeting activities). |
| Attendees | Comma-separated list of attendee email addresses (optional additional field for Meeting activities). |
| Text | Text content of the SMS message (for SMS activities). |
| From | Phone number to send the SMS from (optional additional field for SMS activities). |
| Template ID | Template ID to use for Email or SMS (optional additional field). |
| Additional Fields | Collection of optional fields applicable across activities, such as Contact ID, User who performed the activity, custom creation date, and fields to include in response. |
Output
The node outputs JSON data representing the created activity object(s) as returned by the Close.com API. The structure varies depending on the activity type but generally includes identifiers, timestamps, status, and all relevant details of the created activity.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for Close.com CRM configured in n8n.
- Relies on Close.com REST API endpoints to create activities.
- Uses internal HTTP client methods to communicate with Close.com services.
Troubleshooting
- Invalid Lead ID: If the provided Lead ID does not exist or is invalid, the API will return an error. Verify the Lead ID before running the node.
- Missing Required Fields: Each activity type requires specific fields (e.g., subject for emails, title for meetings). Omitting these will cause errors.
- Email Scheduling Errors: When scheduling emails, ensure the scheduled date is set and valid.
- API Authentication Errors: Ensure the API key credential is correctly configured and has sufficient permissions.
- Rate Limits: Close.com API rate limits may cause temporary failures; implement retry logic or reduce request frequency.
- HTML Formatting Issues: For notes with HTML enabled, malformed HTML can cause unexpected results.