Hosted page
Responsive pages, clear sender context, validation, private or shared links, expiry, and submission limits.
Input, files, and approvals from people
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.
Use the workflow execution id as metadata so the completion webhook resumes the correct automation.
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}]
}{
"status": "completed",
"response": {
"company_name": "Northstar AS"
}
}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.Responsive pages, clear sender context, validation, private or shared links, expiry, and submission limits.
Typed values, authenticated file downloads, correlation metadata, timestamps, and stable response ids.
Polling, signed webhooks, retries with backoff, delivery history, idempotency, and replay.
Start with $1 free. Add funds from $10. Links, polling, webhooks, and abandoned requests do not use the main billable unit.
Create the hosted interaction through Fangst and receive the structured result back.