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 with the Create operation, this node allows users to create new lead records in the Flowyteam system.
This is useful in scenarios where you want to automate lead management workflows, such as capturing new client inquiries from a form or CRM and pushing them into Flowyteam for follow-up and tracking. For example, after receiving a new potential client’s information via a web form, you can use this node to automatically create a lead record with relevant details like client name, next follow-up date, contact info, and notes.
Properties
| Name | Meaning |
|---|---|
| Client Name | The name of the client associated with the lead (required). |
| Next Follow Up | The date and time scheduled for the next follow-up with the lead (required). |
| Additional Fields | Optional extra fields to provide more details about the lead. These include: |
| - Address: Lead's address | |
| - Agent ID: Numeric identifier for the agent handling the lead | |
| - Company Name: Name of the company | |
| - Email: Contact email address | |
| - Meeting Date: Scheduled meeting date and time | |
| - Mobile: Mobile phone number | |
| - Note: Additional notes or comments | |
| - Source ID: Numeric identifier for the lead source | |
| - Status ID: Numeric identifier for the lead status | |
| - Website: Website URL related to the lead |
Output
The node outputs JSON data representing the created lead record as returned by the Flowyteam API. This typically includes all the lead details that were sent plus any additional metadata or identifiers assigned by the system upon creation.
No binary data output is indicated for this operation.
Dependencies
- Requires an active connection to the Flowyteam API.
- Needs an API authentication token or API key credential configured in n8n under the node’s credentials settings.
- The node depends on the Flowyteam service being available and accessible from the environment where n8n runs.
Troubleshooting
Common Issues:
- Missing required fields such as "Client Name" or "Next Follow Up" will cause errors.
- Invalid date/time format for "Next Follow Up" or "Meeting Date" may result in API rejection.
- Network connectivity issues or invalid API credentials will prevent successful lead creation.
Error Messages:
- Errors indicating missing parameters usually mean required inputs were not provided.
- Authentication errors suggest incorrect or expired API keys.
- API response errors might indicate invalid field values or server-side problems; check the exact error message returned by the API for guidance.
Resolution Tips:
- Ensure all required fields are filled correctly.
- Validate date/time formats before sending.
- Verify API credentials and network access.
- Review API documentation for valid field constraints.
Links and References
- Flowyteam official API documentation (refer to your internal or public API docs for detailed field definitions and examples).
- n8n documentation on creating custom nodes and managing credentials.