Webforms

Plant and retire seeds using forms published on your website

Webforms is a deployment type integration that can be used to plant seeds into a webform that you have previously published.

A typical scenario would be a "subscribe me" form on your website where visitors would provide their details so that you could add them to yout marketing actions. Adding seeds into this list can help identify instances of insider theft, 3rd party supplier compromise, or security breach by an external actor.

in order to create your new webform integration, you will need to know the following items:

  • The URL that your form expects to receive submitted data on (you can identify this by looking at the code of the form for its "Action")

  • The list of fields your form expects. Be clear on the names being used, the format of data expected to be sent, and which fields that are mandatory.

If you've got that info, you're ready to go...

Create a new Webform integration

  • Go to https://app.seedata.io/integrations/marketplace and find the Web Form (deployment) integration tile.

  • Click Install, and set a unique name and description that will remind you why you created this integration

  • Enter your Form URL. This is the URL that is expecting the data to be submitted to it. Sometimes this is the form itself, sometimes it is a different URL

  • Add any headers that your form is expecting. You may have created a specific form just for seeding a database, and put it behind authentication, requiring a token be passed in headers

  • Complete the Field Mappings. This is where you build relationships between the values that seedata.io are able to submit, and the names of the fields that your form is expecting. Add as many rows as you need using the "+ Add" button. There are two types of mapping;

    • Dynamic mapping : We will create a new value for every seed, and pass it with the name you provide. These are commonly the seed values, but we've also included a random string/number/ID creator for situations where you need a value but it's not one of our fields.

    • Static mapping : This is used in situations where you always wish to pass the same value for all seeds. You might have a form name value set, or some other variable that does not change. Simply provide the name and the value you wish to pass

  • Click Save

You'll now be able to use this integration as a location for deployments

Last updated