Actions101
- Attendance Actions
- Client Actions
- Department Actions
- Designation Actions
- Employee Actions
- Holiday Actions
- KPI Actions
- KPI Category Actions
- KPI Data Actions
- Lead Actions
- Leave Actions
- OKR Key Result Actions
- OKR Objective Actions
- Performance Cycle Actions
- Project Actions
- Project Category Actions
- Task Actions
- Task Category Actions
- Ticket Actions
- Ticket Agent Actions
- Ticket Channel Actions
- Ticket Type Actions
Overview
The node provides integration with the Flowyteam API to manage various business resources, including leads. Specifically, for the Lead resource and the Update operation, this node updates an existing lead's information in the Flowyteam system. This is useful in scenarios where lead details such as client name, follow-up dates, contact information, or status need to be modified based on new data or interactions.
Practical examples include:
- Updating a lead’s next follow-up date after a sales call.
- Changing the lead’s status or assigned agent after qualification.
- Adding notes or updating contact details as more information becomes available.
Properties
| Name | Meaning |
|---|---|
| Lead ID | The unique identifier of the lead to update (required). |
| Client Name | The name of the client associated with the lead (required). |
| Next Follow Up | The date and time for the next follow-up action with the lead (required). |
| Additional Fields | Optional additional fields to update, which can include: |
| - Address: Lead's address | |
| - Agent ID: Numeric ID of the assigned agent | |
| - Company Name: Name of the company | |
| - Email: Contact email address | |
| - Meeting Date: Date and time of any scheduled meeting | |
| - Mobile: Mobile phone number | |
| - Note: Additional notes about the lead | |
| - Source ID: Numeric ID indicating the source of the lead | |
| - Status ID: Numeric ID representing the lead's current status | |
| - Website: Website URL related to the lead |
Output
The node outputs JSON data representing the updated lead object returned from the Flowyteam API. This typically includes all the lead's properties after the update, reflecting the new state of the lead record.
If the API supports it, the output may also contain metadata about the update operation, such as timestamps or confirmation messages.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Flowyteam API.
- Requires an API authentication token or API key credential configured in n8n under the node's credentials.
- The node depends on the Flowyteam API endpoints for lead management.
Troubleshooting
Common issues:
- Invalid or missing Lead ID will cause the update to fail.
- Incorrect date/time format for "Next Follow Up" or "Meeting Date" fields may result in errors.
- Missing required fields like Client Name or Next Follow Up will prevent successful update.
- Network or authentication errors if API credentials are invalid or expired.
Error messages:
"The operation 'update' is not supported for Lead resource": This indicates a misconfiguration or unsupported operation; ensure the correct resource and operation are selected.- API error responses related to validation failures (e.g., invalid field values) should be checked and corrected accordingly.
- Authentication errors suggest checking the API key or token validity.
Links and References
- Flowyteam official API documentation (for detailed API endpoint info and field definitions).
- n8n documentation on creating custom nodes and managing credentials.
- General REST API best practices for handling updates and error responses.