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
SMS → Find
AI-generatedOverview
This node operation allows users to find SMS messages within the Close CRM system. It supports filtering SMS records by lead ID, user ID, and additional date-based filters such as creation date before or after specified timestamps. Users can choose to return all matching SMS records or limit the number of results returned. This operation is useful for retrieving SMS communication history related to specific leads or users, enabling better tracking and management of SMS interactions in sales or customer support workflows.
Use Case Examples
- Retrieve all SMS messages associated with a particular lead to review communication history.
- Filter SMS messages sent or received by a specific user within a date range to analyze user activity.
- Limit the number of SMS records returned to the most recent 50 for quick overview.
Properties
| Name | Meaning |
|---|---|
| Lead ID | Filter SMS by lead ID to find messages related to a specific lead. |
| User ID | Filter SMS by user ID to find messages associated with a particular user. |
| Additional Filters | Additional filtering options including date created after or before specified dates to narrow down SMS records. |
| Return All | Boolean option to return all matching SMS records or limit the results. |
| Limit | Maximum number of SMS records to return when 'Return All' is false. |
Output
JSON
id- Unique identifier of the SMS message.lead_id- ID of the lead associated with the SMS.user_id- ID of the user associated with the SMS.date_created- Timestamp when the SMS was created.text- Content of the SMS message.status- Status of the SMS message (e.g., sent, received).direction- Direction of the SMS (e.g., inbound, outbound).
Dependencies
- Close CRM API key credential
Troubleshooting
- Ensure that the required parameters such as Lead ID or User ID are correctly provided when filtering.
- If no SMS records are returned, verify that the filters match existing SMS data in the Close CRM account.
- Check API credentials and permissions to ensure the node can access SMS data.
- Common errors include missing required parameters or invalid date formats in filters; ensure dates are correctly formatted ISO strings.
Links
- Close CRM SMS API Documentation - Official API documentation for managing SMS messages in Close CRM.