Create
Use an HTTP Request node with a scoped Fangst API token to define the fields, files, or decision required.
Add external human input to an n8n workflow.
Use an HTTP Request node to create a Fangst request. Send the returned URL through your existing n8n channel and continue when Fangst calls the webhook.
From API call to structured result.
- Create the requestSoftware or an AI agent defines the fields and receives a hosted URL.
- Share the URLA person opens the Fangst page and provides the requested input or files.
- Read the resultFangst returns structured data through the API or a signed webhook.
Create the request from an n8n HTTP node.
Use the workflow execution id as metadata so the completion webhook resumes the correct automation.
Create
POST https://api.fang.st/v1/requests
Authorization: Bearer {{$env.FANGST_API_TOKEN}}
Content-Type: application/json
{
"title": "Complete supplier data",
"metadata": {"execution_id": "{{$execution.id}}"},
"webhook": {"url": "{{$execution.resumeUrl}}"},
"fields": [{"key": "account", "type": "text", "required": true}]
}Completed result
{
"status": "completed",
"response": {
"company_name": "Northstar AS"
}
}Build the n8n wait-and-resume path in three parts.
Fangst supplies the hosted human step, while n8n remains responsible for choosing the recipient and delivery channel. Keep the workflow execution id in metadata so the result can return to the correct run.
Deliver
Send the returned hosted URL through the email, chat, CRM, or ticketing node your workflow already uses.
Continue
Receive and verify the signed completion webhook, match its metadata to the waiting execution, and read the structured result.
Use REST, MCP, polling, or webhooks.
Software uses the HTTP resources directly. Authorized AI agents can use the same API or intention-oriented Fangst MCP tools.
POST/v1/requestsCreate a hosted request and receive its URL.GET/v1/requests/:idRead request status and configuration.GET/v1/requests/:id/submissionsRead completed responses.MCPrequest_human_inputLet an authorized agent create the request.MCPget_human_inputLet the agent read the completed response.Fangst runs the hosted interaction.
Hosted page
Responsive pages, clear sender context, validation, private or shared links, expiry, and submission limits.
Structured result
Typed values, authenticated file downloads, correlation metadata, timestamps, and stable response ids.
Reliable delivery
Polling, signed webhooks, retries with backoff, delivery history, idempotency, and replay.
Pay for completed interactions. No subscription.
Start with $1 free. Add funds from $10. Links, polling, webhooks, and abandoned requests do not use the main billable unit.
Give your software a way to ask people.
Create the hosted interaction through Fangst and receive the structured result back.