Overview
This node generates a web form based on the schema of a specified Appwrite database collection, allowing users to submit data that creates a new document in that collection. It is useful for scenarios where you want to collect data via a customizable web form and automatically store it in an Appwrite database, such as customer feedback forms, data entry forms, or surveys. The node provides a form URL that can be shared and used when the workflow is active.
Use Case Examples
- Create a customer feedback form that submits responses directly to an Appwrite database collection.
- Build a data entry form for internal use to collect and store employee information.
- Set up a survey form that automatically saves responses as documents in a specified collection.
Properties
| Name | Meaning |
|---|---|
| Database ID | The ID of the Appwrite database where the collection resides. |
| Collection ID | The ID of the collection within the database where documents will be created. |
| Form Title | The title displayed at the top of the generated web form. |
| Form Description | Description text shown below the form title to guide users. |
| Submit Button Text | Text displayed on the form's submit button. |
| Success Message | Message shown to users after a successful form submission. |
| Form Theme | Visual theme of the form, affecting colors and styles. |
Output
JSON
document- The newly created document in the Appwrite collection after form submission.submittedData- The processed data submitted through the form, mapped to the collection's attributes.rawFormData- The raw form data as received from the HTTP POST request.success- Boolean indicating whether the form submission and document creation were successful.error- Error message if the document creation failed (present only on failure).
Dependencies
- Appwrite API with credentials including endpoint, project ID, and API key
Troubleshooting
- Ensure the workflow is active; the form URL only works when the workflow is activated.
- Verify that the Database ID and Collection ID are correct and that the collection schema matches the form fields.
- Common errors include failure to load the form (e.g., due to invalid credentials or network issues) and failure to create a document (e.g., due to validation errors or missing required fields).
- Error messages are displayed as HTML pages with details; users can retry submission or check the form configuration.