Formless Responses
FluidGrids has no Formless node, and no "New Response" trigger for Formless, Typeform's conversational AI form product. This page explains why and shows how to get Formless responses into a workflow today.
Why there is no node
Formless gives an outside service no supported way to read responses:
- Formless publishes no API: there is no API reference, no developer portal and no way to register an OAuth app.
- A Formless share cannot send responses to a custom URL. There is no webhook setting, so there is nothing a FluidGrids trigger could register with or that you could paste a FluidGrids URL into.
- Its only integration is Typeform's own Zapier app, which has a single trigger, New Response, and no actions. That app runs on private endpoints that are not documented for other services, and FluidGrids does not build on undocumented endpoints.
- Typeform's public API covers Typeform forms only. Formless shares are not reachable through it, so the Typeform node does not cover Formless.
If Typeform publishes a Formless API or adds a webhook destination, FluidGrids will add a native node and trigger.
Option 1: forward responses from Zapier to a Webhook Trigger
Use this when the form must stay a Formless share. You need a Zapier account; the Zap uses one Zapier task per response.
In FluidGrids
- Create a workflow with a Webhook Trigger and save it. The trigger URL appears on the node.
- Set the trigger's authentication method to API Key Header (or Bearer Token) and copy its secret. Zapier cannot compute the HMAC SHA-256 Signature that the trigger uses by default, so a request signed that way from Zapier would be rejected. Do not choose None: anyone with the URL could then start the workflow.
- Leave Respond on Immediately, so Zapier gets its answer as soon as the run is queued.
- Activate the workflow. The URL starts only the workflow's Active version.
In Zapier
- Create a Zap whose trigger is Formless > New Response, connect your Formless account and pick the share (
share_id). - Add the action Webhooks by Zapier > POST:
- URL: the Webhook Trigger URL from FluidGrids.
- Payload Type:
json. - Data: one entry for each response field you need, mapped from the Formless trigger (for example
email,name,answers,response_id). - Headers:
X-API-Keywith the trigger's secret (or the header name you set on the trigger). For Bearer Token, sendAuthorizationwithBearer <secret>instead.
- Test the action. A run should appear under Runs, and the trigger's delivery log should show the request.
- Turn the Zap on.
The run receives the JSON body as the trigger's output, so later nodes read the fields by the names you set under Data. Use payload mapping on the Webhook Trigger to turn them into named workflow variables.
Things to know
- Partial responses. Formless' New Response fires for every new conversation, finished or not. If you only want finished responses, add a filter step in Zapier, or check a completion field in FluidGrids with an If node before doing anything else.
- Delay. Runs start when Zapier runs the Zap. On Zapier plans that poll, that can be several minutes after the response.
- The secret. Treat the trigger URL and its secret like a password. If either leaks, set a new secret on the trigger and update the Zap's header.
- Each run counts toward your plan's monthly runs. See Plans and Quotas.
Option 2: build the form somewhere FluidGrids can reach
Use this when you do not need Formless' conversational AI.
- A FluidGrids Form Trigger. Build the form in FluidGrids. Every submission starts the workflow straight away, with all of its fields, and no third party sits in between. See Workflows for the Form Trigger, and Squarespace Form Submissions for how to link or embed such a form on a website.
- A Typeform form. Typeform's classic forms have a public API and webhooks. In the form's Connect > Webhooks settings, add the URL of a FluidGrids Webhook Trigger, so each submission starts a run (see Webhooks for securing the trigger). The Typeform node's operations can also list forms and read responses, for example to backfill older submissions.
What does not work
- The Typeform node with a Formless share. It only sees Typeform forms in your account. A Formless share ID is not a Typeform form ID.
- Formless' private endpoints. Calling them with an HTTP Request node would mean copying a browser session token. Such tokens expire, are not meant for other services, and can break without notice. Use Option 1 instead.
Next steps
- Webhooks — the Webhook Trigger in detail: authentication, responses and delivery logs
- Workflows — all trigger types
- Interact Quiz Leads — another tool with no public API
- Troubleshooting