Actions3
Create
AI-generatedSummary
Create a Crunchbase company scrape job
Inputs
- urls (required) — Crunchbase company page URLs — one per line or comma-separated
- jobName — Optional name for this job
- waitForCompletion — Whether to wait for the job to finish and return results. WARNING: Holds an n8n worker while polling — use a separate Get node on a schedule for long-running jobs.
- pollInterval — How often to check if the job is done
- maxWait — Maximum time to wait before timing out
- resultLimit — Maximum number of results to fetch after job completion
Output shape
If waitForCompletion is false, returns the raw Weld API create response JSON (containing jobId). If true, returns an array of result objects each with _jobId, _scraperId, and the resolved data payload after polling completes or times out.
The node splits urls by newline or comma, validates each starts with http:// or https:// and matches allowedDomains (crunchbase.com), then POSTs to /api/jobs/create with {scraperId, name, inputs: [{url}].
Examples
Example 1: Create job without waiting
urls provided, waitForCompletion=false. The node returns the jobId and initial status; a separate Get node can later check status or fetch results.
Example 2: Create job and wait for results
urls, waitForCompletion=true, pollInterval=10, maxWait=300, resultLimit=1000. The node polls /api/jobs/get until status is completed or partial, then fetches /api/jobs/results?jobId=...&limit=1000 and returns the data array.