🔠Review your variable schema
Manage the data you are collecting from responders and sending to your integrations.
Last updated
Manage the data you are collecting from responders and sending to your integrations.
Last updated
As responders go through your flow, you will build up a schema of answer variables from them — either through answers they have given directly, or other methods. You can view and edit all of your variables in the Schema tab.
Variables from questions: Variables you collect from the responder directly when they answer a question. Examples: first_name, dog_breed, pet_type
Externally provided: Variables you can pass through the URL of the flow. This can be helpful to add in information about the responder that they might not be able to answer directly, like their unique ID, or Common examples: UTM source, `
API lookups: you can fetch a new answer from a server that returns JSON responses. This lookup can even use other variables collected with the flow as inputs or parameters. Examples are calling your own healthcare provider database, finding the nearest store location, or looking up current pricing.
Calculated inline: Allow you to define new answers based on other answers present within the flow, by writing simple javascript functions that are evaluated within Formsort. A common example is calculating age from a responder’s inputted date of birth (see here)
System library: Variables you can collect about the responder's experience with your flow. Examples include: current_step_id, is_mobile, is_returning_responder.
