Comment on page
Actions
When a user clicks buttons, text, or containers on your form, you can trigger a wide variety and sequence of form actions to occur.
When a user clicks buttons, text, or containers on your form, you can trigger a wide variety and sequence of actions to occur.
This action runs before any other action you specify. It will validate all of the field entries on the current step and short-circuit any subsequent actions if it catches a validation error (missing field value, failed custom validation rule, etc.)
If validation completes successfully, it will save the field data to Feathery.
- Go to next step
- Optional allow validating and submitting the fields on your current step
- If validation fails, navigation will not occur.
- Go to previous step
- Navigates back to the last step that the user was on.
You can configure an element to save a custom value into a form or hidden field when it is clicked. This allows you to:
- Track which elements were clicked for calculating navigation, validation, purchases, and more.
- Build custom fields by combining buttons and containers that store custom values into the same hidden field.
Clicking an element can trigger a custom URL to open, either in the same window or in a new tab.
Links also support field variable interpolation. You can use
{{<field_id>}} syntax within the link you define, and Feathery will automatically replace it with the current session's field value before opening the link. To insert the user ID of your current session, use {{feathery_user_id}}If you've set a container on your form as repeating, clicking an element with the
Add Repeating Container action will cause a new copy of the container to appear right below the current one. You can keep triggering the action to continue adding more repetitions after each other.Clicking an element with the
Delete Repeating Container action will have the opposite effect. This element must be within the repeating container itself, and the action will remove the repeating container that contains the element.When an authentication integration like Stytch or Firebase is connected to your form, you have access to verification actions that can be triggered via a click. This includes:
- Log out users that have been logged in
If you have
Remember User turned on in your form settings, you can still allow users to manually initiate new submissions by specifying Start New Submission as a click action. When your user clicks the element, it will trigger a new form session to begin that corresponds to a new submission and new tracked user.Under the hood, this refreshes the cookie being used to track and identify the form user.
Specifying a custom action to run won't do anything automatically. However, if you have a logic rule specified that runs when an element is clicked, or if you've embedded your form and specified a custom action as a callback function, your logic will be run when the user clicks the element.
This is useful if you're starting a collaborative submission directly. This allows you to specify the other collaborators on your submission via the form itself. You'll need to specify the field to pull their email from, along with which collaborator they map to (defined via your collaboration template). You won't be able to use this action unless you've defined your collaboration template with more than one collaborator.
This action will error and short-circuit if the field you associate with this action does not contain the email of a collaborator on the submission. This is useful if you want to set up an initial validation step so even if someone is able to access a collaborative submission link, they won't be able to proceed until they validate the email of the user it belongs to.
For example, you might be the second reviewer in a sequence and have caught a mistake from the previous form filler. This action allows the reviewer to send a form back to an earlier collaborator in the sequence so they can review and re-edit their form entry.
If the collaboration sequence is ordered, the collaborator flow will restart from the collaborator specified in the return action and go through every collaborator after them as well.
If the collaboration sequence is unordered, only the collaborator specified in the return action will need to re-review their submission.
Last modified 7d ago