Actions7
- Enrichment Actions
- Linkedin Actions
Enrichment → Email Pattern
AI-generatedOverview
The Piloterr node for n8n, when configured with the "Enrichment" resource and the "Email Pattern" operation, allows users to look up the typical email address pattern used by a company based on its domain. This is useful in scenarios such as:
- Automating lead generation workflows by predicting possible email addresses for contacts at a given company.
- Enriching CRM data with standardized email formats.
- Verifying or guessing email addresses for outreach campaigns.
Example use case:
Given the domain gucci.com, the node can return the standard email format (e.g., {first}.{last}@gucci.com) used by that organization.
Properties
| Name | Type | Meaning |
|---|---|---|
| Domain | String | The domain to look up. For example, gucci.com. Required input field. |
Output
The node returns a JSON object containing the email pattern information for the specified domain. While the exact structure depends on the API response, it typically includes fields such as:
{
"email_pattern": "{first}.{last}@gucci.com",
"domain": "gucci.com",
// ...other metadata if provided by the API
}
- email_pattern: The standard format used for company emails.
- domain: The queried domain.
Note: The output does not include binary data.
Dependencies
- External Service: Requires access to the Piloterr API.
- API Key: You must configure valid Piloterr API credentials in n8n under the name
piloterrApi.
Troubleshooting
Common Issues:
- Invalid or missing API key: If your API credentials are incorrect or missing, the node will throw an authentication error. Ensure you have set up the
piloterrApicredential in n8n. - Domain not found: If the provided domain does not exist or is not recognized by Piloterr, the response may be empty or contain an error message.
- API rate limits: Excessive requests may result in rate limiting by the Piloterr API. Check your API usage and consider upgrading your plan if needed.
Error Handling:
- If "Continue On Fail" is enabled, errors for individual items will be returned in the output with an
errorfield containing the error message.