Actions5
- Document Actions
- Tag Actions
Document → Create
AI-generatedOverview
This node integrates with the Jalvis.ai API to manage documents and tags. Specifically, for the Document - Create operation, it allows users to create a new document in the Jalvis system by providing various metadata and content fields.
Typical use cases include:
- Automating document creation workflows where documents need to be programmatically added to Jalvis.ai.
- Creating structured records of meetings, reports, or notes with associated participants, categories, and timestamps.
- Organizing documents hierarchically by specifying parent documents.
For example, you could use this node to automatically create a meeting summary document with participants and tags after a calendar event ends.
Properties
| Name | Meaning |
|---|---|
| Title | The title or name of the document (required). |
| Summary | A brief description or summary of the document. |
| Participants | Participants as a comma-separated string. |
| Participant Set | Participants as an array of strings (multiple selection). |
| Categories | Tags/categories assigned to the document (multi-select loaded dynamically from API). |
| Created | The creation date/time of the document (required). |
| Parent ID | ID of the parent document to establish hierarchy (optional). |
| Body | The main text content of the document. |
| Additional Prop1 | Additional custom properties as a JSON object (optional). |
Output
The node outputs the created document's data as JSON. This includes all fields returned by the Jalvis.ai API after successful creation, such as the document ID, title, timestamps, participants, tags, and any other metadata.
If the API returns a string response, the node attempts to parse it as JSON before outputting.
No binary data is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Jalvis.ai API.
- The node expects the base URL and API token/version to be configured in the credentials.
- Network access to the Jalvis.ai API endpoint is necessary.
Troubleshooting
Common issues:
- Invalid or missing API credentials will cause authentication errors.
- Incorrectly formatted JSON in "Additional Prop1" may cause parsing errors.
- Providing invalid dates or empty required fields will result in API validation errors.
Error messages:
- Errors from the API are captured and returned in the output under an
errorfield along with debug information about the request. - If the node fails due to malformed JSON in additional properties, ensure the JSON syntax is correct.
- Network or timeout errors indicate connectivity issues with the Jalvis.ai service.
- Errors from the API are captured and returned in the output under an
To resolve errors, verify credentials, input formats, and network connectivity.
Links and References
- Jalvis.ai API Documentation (Assumed, please replace with actual URL if available)