FetchFox
Get started

Connect FetchFox to n8n with HTTP Request

Use n8n’s built-in HTTP Request node to call the FetchFox REST API. This is a generic HTTP integration; a dedicated FetchFox community node is not required.

Try with free creditsRead as Markdown

Export comments to a spreadsheet

Separate manual starters request one Instagram or Facebook comments batch and create a CSV. Each successful run costs one credit; they do not paginate or retry automatically.

Download a ready-to-import starter

Choose a workflow below, then use Import from File in n8n. Both use a Manual Trigger, stop on failures and have automatic retries disabled. The transcript starter makes one request; creator research makes up to three sequential requests for a profile, 20 posts and 20 reels. No credentials are included in either file.

  1. Import the JSON file into n8n.
  2. Edit Configure input with one public video or profile URL.
  3. Create a Header Auth credential with name x-access-key and your FetchFox project key as its value.
  4. Select that credential in every Fetch node. Keep the key out of node parameters and workflow exports.
  5. Check the request budget, then choose Execute workflow. Read Transcript output or Creator report. These workflows do not schedule runs, paginate feeds or send notifications.
Download transcript workflow · up to 1 creditDownload creator research · up to 3 credits

Configure one transcript request yourself

Create an n8n Header Auth credential with name x-access-key and value set to your FetchFox project key. Keep the key in the credential store rather than embedding it in an exported workflow.

  1. Add a Manual Trigger and an HTTP Request node.
  2. Set Method to GET and URL to https://api.fetchfox.net/youtube/transcript.
  3. Choose Generic Credential Type, Header Auth, and the credential you created.
  4. Enable query parameters; set url to the complete YouTube video URL.
  5. Choose JSON response handling and execute one request. Inspect data.transcript and data.transcriptSegments.

Switch to keyword discovery

For TikTok discovery, change the URL to https://api.fetchfox.net/tiktok/search. Remove the url query parameter and add query=ceramics and limit=20. Keep the same authentication credential. The field names differ by operation; use the endpoint reference when switching.

Only then add scheduling and storage

Map the successful response into your own data store before adding a Schedule Trigger. Store a source identifier and retrieval time, and deduplicate repeated results before notifying anyone.

A daily workflow with one successful one-credit request per day would exceed the 20 free monthly credits. Start with manual or weekly runs. Set a bounded timeout, inspect failures, and honor Retry-After instead of turning on unlimited retries. Review n8n execution-history settings before storing responses that need restricted access.

Sources

External documentation checked October 13, 2026. Client interfaces and third-party capabilities can change.

Continue building