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
This node provides integration with the Flowyteam API, allowing users to manage various resources such as leads, tickets, projects, employees, and more. Specifically for the Lead resource with the Delete operation, the node enables deleting a lead record by its unique identifier. This is useful in scenarios where outdated or incorrect lead data needs to be removed from the system to maintain clean and accurate records.
Practical examples include:
- Automatically removing leads that have been marked as invalid or duplicates.
- Cleaning up leads after a certain period of inactivity.
- Integrating with other systems to delete leads when they are deleted elsewhere.
Properties
| Name | Meaning |
|---|---|
| Lead ID | The unique identifier of the lead to delete. This is a required string input. |
Output
The output of the delete operation typically contains a JSON object indicating the result of the deletion request. This may include confirmation of successful deletion or details about the deleted lead. The exact structure depends on the API response but generally confirms whether the lead was successfully deleted.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Flowyteam API.
- The node must be configured with valid credentials to access the Flowyteam service.
- Network connectivity to the Flowyteam API endpoint is necessary.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Lead ID will likely cause the API to return an error indicating the lead could not be found.
- Missing or invalid API credentials will prevent the node from authenticating and performing the delete operation.
- Network issues or API downtime can cause request failures.
Error messages and resolutions:
- "Lead not found" — Verify the Lead ID is correct and exists in the system.
- "Authentication failed" — Check that the API key credential is correctly set up and has proper permissions.
- Timeout or network errors — Ensure stable internet connection and that the Flowyteam API is reachable.
Links and References
- Flowyteam official API documentation (refer to their website or developer portal for detailed API specs).
- n8n documentation on creating and using custom nodes with API integrations.