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
Custom Activity → Create
AI-generatedOverview
This node operation creates a custom activity associated with a specific lead in the Close CRM system. It allows users to specify the lead ID, the type of custom activity, status, creation date, and user attribution. Additionally, it supports adding various custom fields such as text, rich text, number, date, choice (single or multiple), and user fields (single or multiple) to the custom activity. This operation is useful for tracking and logging custom interactions or events related to leads that are not covered by standard activity types.
Use Case Examples
- Creating a custom activity to log a unique event for a lead, such as a special campaign interaction.
- Adding detailed custom field data to a custom activity to capture specific information relevant to the business process.
Properties
| Name | Meaning |
|---|---|
| Lead ID | The ID of the lead to create the activity for, required to associate the custom activity with the correct lead. |
| Custom Activity Type Name or ID | The type of custom activity to create, selected from a list or specified by ID, required to define the nature of the custom activity. |
| Status | The status of the activity, optional, can be 'draft' to create without all required fields or 'published'. |
| Date Created | Override the date and time when the custom activity happened, optional. |
| User | User to attribute the activity to, selected from a list or specified by ID, optional. |
| Custom Fields | Add custom field values for this custom activity, supporting multiple types such as text, rich text, number, date, choice (single or multiple), and user fields (single or multiple). |
Output
JSON
id- The unique identifier of the created custom activity.lead_id- The ID of the lead associated with the custom activity.custom_activity_type_id- The ID of the custom activity type.status- The status of the custom activity.date_created- The date and time when the custom activity was created.user_id- The ID of the user attributed to the custom activity.custom_fields- The custom fields and their values associated with the custom activity.
Dependencies
- Close CRM API authentication token or API key credential
Troubleshooting
- Ensure that the Lead ID and Custom Activity Type ID are provided as they are required fields; missing these will cause errors.
- Verify that custom field IDs and values are correctly specified and match the expected types to avoid payload construction errors.
- Check API authentication credentials and permissions to ensure the node can successfully communicate with the Close CRM API.
- If the node throws JSON parsing errors, verify that any JSON expressions used in fields like schedule or steps are correctly formatted.
Links
- Close CRM Node Documentation - Official documentation for the Close CRM node in n8n, including usage and configuration details.