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 → Get
AI-generatedOverview
This node interacts with the Close CRM API to perform operations related to SMS activities. Specifically, for the 'Get' operation under the 'SMS' resource, it fetches the details of a specific SMS message by its ID. This is useful in scenarios where you need to retrieve information about a particular SMS sent or received within the Close CRM system, such as for auditing, tracking communication history, or displaying SMS details in an application.
Use Case Examples
- Retrieve details of an SMS by providing its SMS ID to view message content, status, and metadata.
- Use in workflows to fetch SMS information for reporting or further processing.
Properties
| Name | Meaning |
|---|---|
| SMS ID | The ID of the SMS to fetch. This is a required string input that specifies which SMS record to retrieve from Close CRM. |
Output
JSON
id- The unique identifier of the SMS.lead_id- The ID of the lead associated with the SMS.to- The recipient phone number(s) of the SMS.local_phone- The local phone number used to send the SMS.status- The current status of the SMS (e.g., sent, received).text- The text content of the SMS message.date_created- The date and time when the SMS was created.date_scheduled- The scheduled date and time for sending the SMS, if applicable.direction- The direction of the SMS (e.g., inbound or outbound).template_id- The ID of the template used for the SMS, if any.
Dependencies
- Close CRM API access with appropriate API key or credentials
Troubleshooting
- Common issues include missing or invalid SMS ID, which will cause the node to throw an error indicating the SMS ID is required for the get operation.
- API authentication errors if the Close CRM API credentials are not set up correctly.
- Network or API endpoint issues that prevent successful communication with the Close CRM API.
Links
- Close CRM API - SMS - Official Close CRM API documentation for SMS resource and operations.