Actions104
- Custom Field Actions
- Custom Field Block Actions
- Custom Field Type Actions
- Customer Actions
- Deal Actions
- Lead Actions
- Meeting Actions
- Meeting Room Actions
- Meeting Type Actions
- Organization Actions
- Pipeline Actions
- Prospect Actions
- Staff Actions
- Task Actions
- Ticket Actions
- Treatment Actions
- Treatment Type Actions
- Workspace Actions
Meeting Type → Update
AI-generatedOverview
This node updates a Meeting Type in the Magnet Customer system. It is useful for scenarios where you need to modify the details of an existing meeting type, such as changing its name or other attributes. For example, if a meeting type's purpose or title changes, this node allows you to update that information programmatically within an automation workflow.
Use Case Examples
- Updating the name of a specific meeting type by providing its ID and the new name.
- Modifying meeting type details to reflect changes in scheduling or categorization.
Properties
| Name | Meaning |
|---|---|
| Authentication | Selects the authentication method to use for the API request (API Token or OAuth2). |
| Type ID | The unique identifier of the meeting type to update. This is required to specify which meeting type to modify. |
| Name | The new name to assign to the meeting type. This is optional and used to update the meeting type's name. |
Output
JSON
_id- The unique identifier of the updated meeting type.name- The updated name of the meeting type.createdAt- Timestamp when the meeting type was created.updatedAt- Timestamp when the meeting type was last updated.
Dependencies
- Magnet Customer API with either API Token or OAuth2 authentication
Troubleshooting
- Ensure the provided Type ID is correct and exists in the Magnet Customer system; otherwise, the update will fail.
- Verify that the authentication credentials (API Token or OAuth2) are valid and have sufficient permissions to update meeting types.
- If the 'Name' field is left empty, the meeting type's name may not be updated as expected.
- Common error messages may include authorization errors, resource not found, or validation errors for the input fields. Check the error message details to resolve issues.