Before you start
- n8n instance (cloud or self-hosted)
- CatchAll API key (obtain from platform.newscatcherapi.com)
Install community node
1
Open community nodes settings
Navigate to Settings → Community Nodes in your n8n instance.
2
Install the CatchAll node
Enter the package name:
n8n-nodes-newscatcher-catchall-pernode Click
Install and wait for the installation to complete.3
Verify installation
Create a new workflow and search for “Newscatcher” in the node panel. The CatchAll node should appear in your available nodes.
Configure credentials
1
Add CatchAll credentials
In any workflow, add the Newscatcher CatchAll node. Click the Credential to connect with dropdown and select Create New Credentials.
2
Enter your API key
Paste your CatchAll API key into the credential field and click Save.
Credentials are stored securely in your n8n instance and reused across
workflows.
Create your first workflow
This example submits a CatchAll job, polls for completion, and retrieves results:1
Submit a job
Add a Newscatcher CatchAll node with these settings:
- Operation: Submit Job
- Query:
Tech company earnings this quarter - Context:
Focus on revenue and profit margins - Schema:
Company [NAME] earned [REVENUE] in [QUARTER]
job_id for the next step.2
Wait for job completion
Add a Wait node set to 10 minutes. CatchAll jobs typically complete in
10-15 minutes.
3
Check job status
Add another Newscatcher CatchAll node:
- Operation: Job Status
- Job ID:
{{ $json.job_id }}(from Submit Job node)
completed in the steps array.4
Pull results
Add a final Newscatcher CatchAll node:
- Operation: Pull Job Results
- Job ID:
{{ $json.job_id }}
enrichment object containing extracted data.Available operations
The CatchAll node supports these operations:Job operations
| Operation | Description | Use Case |
|---|---|---|
| Submit Job | Create a new CatchAll job | Start structured web research |
| Job Status | Check processing progress | Poll until completion |
| Pull Job Results | Retrieve structured records | Get final data with citations |
| List User Jobs | Get all jobs for your API key | View job history |
Monitor operations
| Operation | Description | Use Case |
|---|---|---|
| Create Monitor | Schedule recurring jobs | Automate periodic research |
| List Monitors | View all active monitors | Manage scheduled jobs |
| List Monitor Jobs | Get execution history | Track monitor runs |
| Pull Monitor Results | Get aggregated records | Retrieve all monitor data |
| Enable Monitor | Resume a paused monitor | Restart automation |
| Disable Monitor | Pause a running monitor | Stop scheduled execution |
Common workflows
Research automation
Automatically research companies and export to your CRM:- Trigger: Schedule (daily at 9 AM)
- CatchAll: Submit job with company query
- Wait: 10 minutes
- CatchAll: Pull results
- Transform: Map fields to CRM format
- CRM Node: Create/update records
Scheduled monitoring
Set up recurring research with webhook notifications:- CatchAll: Create monitor with webhook URL
- Webhook Trigger: Listen for completion
- CatchAll: Pull monitor results when triggered
- Process: Transform and route data
- Notification: Send summary to Slack/email
Multi-source enrichment
Combine CatchAll with other data sources:- Spreadsheet: Load list of companies
- Loop: For each company
- CatchAll: Submit research job
- Wait: For completion
- CatchAll: Pull results
- Merge: Combine with existing data
- Spreadsheet: Write enriched data
Troubleshooting
Node not found after installation
Solution: Restart your n8n instance. For self-hosted installations, restart the Docker container or service.API key not recognized
Symptom: 403 Forbidden error Solution: Verify your API key is active in the platform dashboard. Create new credentials if needed.Job takes too long
Symptom: Job doesn’t complete after 20 minutes Solution: Check job status using the Job Status operation. If stuck in a processing stage, contact support with thejob_id.
Empty enrichment object
Symptom: Results return butenrichment contains no fields
Solution: The query may be too broad or no matching content was found. Try
refining your query with more specific context.

