Sending data elsewhere
Records are yours. There are six ways to get them out of FormDragon and into whatever you use next, and the right one depends on how often and how automatically you need it.
| You want to… | Use |
|---|---|
| grab a form’s records now, as a file | Export — CSV or JSON |
| pull records on a schedule from your own system | The API |
| be told the moment a record arrives or changes | Webhooks |
| keep a spreadsheet up to date automatically | Google Sheets |
| connect to a tool that has a Zapier app | Zapier |
| turn each record into a PDF or Word document | DragonDocs |
The recipes on the following pages show how these combine to reach SQL Server, Power BI and Formstack Documents, none of which have a connector of their own.
What every route has in common
- Field keys are the column names. Whatever you connect will see
reading_end, not “Hour meter, finish”. Stable keys are what keep a downstream report working — see Field keys. - Choice fields carry the stored value, not the label:
northgate, not Northgate Depot. Map values to labels on the receiving side, or use the label field the export offers. - Repeatable sections are a list inside the record. In a flat file they arrive as one column holding the rows; in JSON they are an array. Subform entries are separate records on the child form.
- Access is the same as on the web. The API and export only return what the signed-in person could see on screen.
Need your data somewhere these pages do not cover? Write to customer.service@firedragontech.com and tell us what you are trying to reach. We will help you get the data there — that is the point of collecting it.