Actions36
- Activity Actions
- Contact Actions
- Customer Actions
- Data Proxy Actions
- Document Actions
- Employer Actions
- Lead Actions
- Meeting Actions
- Meeting Summary Actions
- Report Actions
- Workflow Actions
Meeting Summary → Send a Meeting Summary
AI-generatedOverview
The "Send a Meeting Summary" operation in the Meeting Summary resource allows users to send a meeting summary to specified recipients via SMS and/or email. This node is useful for automating the distribution of meeting notes or summaries to customers or stakeholders immediately after a meeting concludes, ensuring timely communication and follow-up.
Practical examples include:
- Sending a summary of a sales meeting to a client’s phone number(s) and email address(es).
- Distributing internal meeting notes to team members who prefer receiving updates via SMS or email.
- Automating customer communications by sending meeting summaries directly from your CRM or workflow system.
Properties
| Name | Meaning |
|---|---|
| מזהה לקוח (customerId) | Customer ID in UUID format identifying the recipient customer. Required. |
| מזהה סיכום פגישה (meetingSummaryId) | Meeting Summary ID in UUID format specifying which meeting summary to send. Required. |
| Additional Parameters | Optional collection of additional parameters: |
| - מספרי פלאפון (cellNumbers) | List of one or more cell phone numbers (in international format, e.g., +972502333327) to send the SMS message to. |
| - מיילים (emails) | List of one or more email addresses to send the meeting summary to. |
Output
The node outputs JSON data representing the result of the send operation for each input item. The exact structure depends on the API response but typically includes success confirmation or error details per recipient.
If the node supports binary data output (not indicated here), it would represent attachments or documents related to the meeting summary, but this is not evident from the provided code or properties.
Dependencies
- Requires an API key credential for authenticating with the Surense API.
- The node depends on the Surense service to perform operations related to meetings and meeting summaries.
- Proper configuration of the OAuth2 API credentials within n8n is necessary for successful execution.
Troubleshooting
Common issues:
- Invalid or missing Customer ID or Meeting Summary ID (must be valid UUIDs).
- Incorrectly formatted phone numbers or email addresses may cause delivery failures.
- Authentication errors if the API key or OAuth2 token is invalid or expired.
- Network connectivity issues preventing access to the Surense API.
Error messages:
- Errors returned from the API will be included in the output JSON under an
errorfield. - If the node is set to continue on fail, errors for individual items will not stop the entire workflow but will be reported per item.
- To resolve errors, verify all IDs and contact information, ensure valid credentials, and check network connectivity.
- Errors returned from the API will be included in the output JSON under an
Links and References
- Surense API Documentation (replace with actual URL)
- n8n documentation on Creating Custom Nodes
- General best practices for UUID formatting
- Guidelines for International Phone Number Formatting
Note: The above summary is based solely on static analysis of the provided source code and property definitions without runtime execution.