Weld Twitter/X Posts icon

Weld Twitter/X Posts

Extract tweets from Twitter/X post URLs

Actions3

Create

AI-generated

Summary

Submit Twitter/X post URLs to create a scrape job on Weld's platform.

Inputs

  • urls (required) — Twitter/X post URLs (x.com/user/status/id) — 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
  • 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

The operation returns data based on the waitForCompletion setting: without completion wait, the raw API job-creation response (containing at minimum a jobId). With waitForCompletion enabled, the node polls the job status periodically and, upon completion, returns an array of result objects each containing _jobId, _scraperId, and the scraped data field. If the job fails, a NodeOperationError is thrown. If polling exceeds maxWait seconds, the node returns { json: { jobId, status: 'timeout', message: 'Job did not complete within...' } }.

URLs are split on newlines and commas, trimmed, and validated against allowed domains (twitter.com, x.com). The job is submitted via POST to https://actions.useweld.app/api/jobs/create with body { scraperId: 'twitter-posts', name: <jobName || undefined>, inputs: [{ url }] }.

Examples

Example 1: Quick job submission without waiting

Provide URLs; leave waitForCompletion at default false. The node returns the job creation response immediately, allowing a separate Get node to check status later.

Example 2: Full scrape with results

Provide URLs; set waitForCompletion to true (optionally adjust pollInterval and maxWait). The node blocks an n8n worker while polling, then returns up to resultLimit results from the completed job.

Links

Discussion