Actions16
- 📧 Email Actions
- 🏢 Company Actions
- 👤 Profile Actions
- 👥 People Actions
- 💼 Job Actions
- 📱 Advertisement Actions
Overview
The "Find Role" operation in the 👥 People resource of this node enables users to search for employees holding a specific job title or role within a company. It supports specifying the target company by one of three methods: company domain, company profile URL, or company name. This flexibility allows users to tailor their search based on the information they have available.
This node is beneficial in scenarios such as:
- Recruiting professionals with a particular job title at a known company.
- Sales prospecting by identifying decision-makers or relevant contacts within target organizations.
- Market research to understand team compositions in competitor companies.
For example, a user could find all "Developers" working at "microsoft.com" by specifying the job title and using the domain search method.
Properties
| Name | Meaning |
|---|---|
| Job Title | The job title or role to search for (e.g., Developer). |
| Search Method | How to specify the company; options are: |
| - By Domain: Most accurate method, search by company domain (e.g., microsoft.com). | |
| - By Profile URL: Search by company profile URL. | |
| - By Company Name: Search by company name (less accurate). | |
| Company Name | The name of the company (shown only if Search Method is "By Company Name"). |
| Company Domain | The domain of the company (shown only if Search Method is "By Domain"). |
| Company Profile URL | The profile URL of the company (shown only if Search Method is "By Profile URL"). |
Output
The node outputs JSON data representing the results returned from the role-finder API endpoint. Each item in the output array corresponds to a found person matching the specified job title within the given company context.
The exact structure depends on the external API response but typically includes details about the person’s role, contact information, and possibly company-related metadata.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating requests to the external LeadMagic API service.
- The node makes HTTP POST requests to the endpoint
https://api.leadmagic.io/role-finder. - Proper configuration of the API authentication credential in n8n is necessary.
Troubleshooting
Common Issues:
- Providing an invalid or empty job title will likely result in no matches or an error.
- Using an inaccurate company identifier (especially when using company name) may yield incomplete or incorrect results.
- Network or authentication errors if the API key is missing, invalid, or expired.
Error Messages:
- Errors related to exceeding input limits or malformed requests will be returned by the API and surfaced by the node.
- Authentication failures will indicate issues with the provided API key credential.
Resolutions:
- Ensure the job title is correctly spelled and meaningful.
- Prefer using company domain or profile URL for more accurate searches.
- Verify that the API key credential is correctly set up and has sufficient permissions.
- Check network connectivity and API service status if requests fail unexpectedly.
Links and References
- LeadMagic API Documentation (for detailed API usage and parameters)
- n8n Documentation (for general node usage and credential setup)