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
Meeting → Update
AI-generatedOverview
This node updates an existing meeting record in the Close CRM system. It is useful for scenarios where you need to modify details of a meeting, such as adding user notes or updating the meeting outcome. For example, after a meeting concludes, you might want to add a summary note or change the outcome status to reflect the meeting's result.
Use Case Examples
- Updating a meeting to add a user note summarizing the discussion.
- Changing the outcome ID of a meeting to indicate the meeting's result.
Properties
| Name | Meaning |
|---|---|
| Meeting ID | The ID of the meeting to update, used to identify which meeting record to modify. |
| Update Fields | A collection of fields that can be updated for the meeting, including user notes and outcome ID. |
Output
JSON
id- The unique identifier of the updated meeting.user_note_html- The user note content in HTML format after update.outcome_id- The updated outcome ID of the meeting.
Dependencies
- Close CRM API key credential for authentication
Troubleshooting
- Common errors include missing required parameters such as Meeting ID, which will cause the node to throw an error indicating the missing field.
- Invalid format in the user note or outcome ID fields may cause the API request to fail; ensure the user note is plain text and will be converted properly to HTML.
- API request failures due to network issues or invalid credentials will result in errors; verify API key and network connectivity.
Links
- Close CRM API - Update a Meeting - Official API documentation for updating a meeting in Close CRM.