Actions6
- Job Actions
- Tool Actions
Overview
This node integrates with the Workfloows API to extract company contact information from a specified company website URL. It sends a request to crawl the given company website and retrieves contact details such as emails, phone numbers, names, or other relevant contact data found on the site.
Common scenarios where this node is beneficial include:
- Building lead generation workflows by automatically gathering contact info from company websites.
- Enriching CRM records with verified contact details scraped directly from official company pages.
- Automating outreach campaigns by collecting up-to-date contacts without manual research.
For example, you can input the URL of a target company’s homepage, and the node will return a structured list of contacts associated with that company, simplifying the process of finding decision-makers or support contacts.
Properties
| Name | Meaning |
|---|---|
| URL | Full URL of the company web page to scrape (including protocol, e.g., https://example.com). |
| Simplify | Whether to return a simplified version of the response instead of the raw detailed data. |
Output
The node outputs JSON data containing the contact information extracted from the specified company website.
- If Simplify is enabled (default), the output contains a streamlined, easy-to-use structure with key contact details.
- If Simplify is disabled, the output includes the full raw response from the API, which may contain additional metadata or nested data structures.
The output does not include binary data; it is purely JSON-formatted contact information.
Dependencies
- Requires an active connection to the Workfloows API.
- Requires an API authentication token credential configured in n8n for accessing the Workfloows service.
- The node makes HTTP POST requests to the endpoint:
https://api.workfloo.ws/v0/companies/contacts.
Troubleshooting
- Invalid or missing URL: Ensure the URL property is a valid, fully qualified URL including the protocol (
http://orhttps://). Invalid URLs will cause the API call to fail. - Authentication errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- Empty or incomplete contact data: Some websites may restrict scraping or have dynamic content that the API cannot access. Try verifying the URL manually or using alternative sources.
- API rate limits or downtime: If requests fail repeatedly, check your API usage limits or the Workfloows service status.
Links and References
- Workfloows API Documentation (for detailed API capabilities and response formats)
- n8n HTTP Request Node Documentation (for understanding how HTTP requests are made within n8n)