Skip to content
Jotform logoFeathery logo

Connect Jotform to Feathery

Move data between Jotform and Feathery the moment it happens. Build the flow visually, or let AI write it for you, then run it on our cloud or your own infrastructure.

Jotform triggers
1
Jotform actions
1
Feathery triggers
3
Feathery actions
5

Automation ideas

What you can build with Jotform and Feathery

A few flows teams run between Jotform and Feathery. Use one as a starting point, or build your own from scratch.

  • New Submission in Jotform creates Create Form in Feathery

    Triggers when someone submits a response to your form. Each form field is returned as a separate field using the question label as the key.

  • New Form Submission in Feathery creates Custom API Call in Jotform

    Triggers when a user submits data through your form.

  • New Submission in Jotform creates Update Form in Feathery

    Triggers when someone submits a response to your form. Each form field is returned as a separate field using the question label as the key.

  • Form Completed in Feathery creates Custom API Call in Jotform

    Triggers when a form is completed by an end user.

  • New Submission in Jotform creates Delete Form in Feathery

    Triggers when someone submits a response to your form. Each form field is returned as a separate field using the question label as the key.

  • File Submitted in Feathery creates Custom API Call in Jotform

    Triggers when a file is submitted in your form, or when a document is signed/generated.

Questions, answered

No. Pick a trigger on either piece and an action on the other, map the fields, and turn the flow on. Add a code step later only if you want to.

Yes. Build one flow that starts in Jotform and acts in Feathery, and a second that runs the other way, in the same project.

On our EU cloud in Frankfurt, or self-hosted on your own infrastructure with Docker or Kubernetes. The MIT-licensed core means there is always an exit.