Back to FAQ

Import, documents, and webhooks without overclaiming integrations

Short answers about verified CSV import, dry runs, import history, document templates, generated HTML and PDF files, AI-assisted template drafts, signed outbound webhooks, and what should not be described as native two-way integrations.

CSV and XLSX uploads, templates, dry runs, partial or all-or-nothing mode, column mapping, job history, and queued large imports
Sandboxed Jinja2 templates, generated HTML and PDF output, client/pet/patient/appointment merge data, and optional AI-assisted template drafts
Admin-managed endpoints, HMAC-SHA256 signatures, wildcard or named events, queued delivery, retries, delivery logs, tests, and failure auto-disable

What does Tregovia cover for imports, documents, and webhooks?

Tregovia covers this area through three modules. Data Import handles CSV or XLSX uploads for supported entity types. Documents manages reusable templates and generated documents. Webhooks sends signed HTTP events to external systems when Tregovia events are published.

What can the Data Import module import?

The verified import types are clients, pets, vaccinations, services, appointments, invoices, products, patients, prescriptions, and logistics inventory items. Imports support downloadable templates, dry-run validation, partial or all-or-nothing processing, optional column mapping, recent job history, and queued processing for larger non-dry-run files above the synchronous row threshold.

What can the Documents module generate?

Documents can store reusable HTML templates with sandboxed Jinja2 variables, validate template syntax, render previews, persist generated documents, serve generated HTML, and create downloadable PDF versions. Verified merge-data contexts are client, pet, patient, and appointment; pet, patient, and appointment documents can also include the linked client when available.

Can AI draft document templates or document sections?

Yes, with boundaries. Admin users can request an AI-assisted template draft when both Documents and AI Composer are enabled. Generated documents can also resolve a small set of AI narrative placeholders before rendering. The AI output is draft content inside the document workflow, not an autonomous send or approval process.

How do webhooks work in Tregovia?

Admins can create active webhook endpoints with event subscriptions or a wildcard subscription. Deliveries are JSON POST requests signed with HMAC-SHA256, include event and delivery headers, are queued for background delivery, retry on failures, store delivery logs, support test sends, and can auto-disable an endpoint after repeated failures.

Which import, document, and integration claims are not verified?

Do not describe Tregovia as having native Zapier or Make connectors, bidirectional sync, Google Drive or Dropbox document storage sync, DocuSign-style embedded signing in the Documents module, automatic duplicate merging, arbitrary-object imports, live migration from every competitor API, or document generation for every module. Claims should stay tied to verified CSV/XLSX imports, templates, generated HTML/PDF documents, AI-assisted drafts, and outbound signed webhooks.

How are these modules priced?

Data Import is included in the base platform. Documents is a shared add-on priced at EUR 5/month. Webhooks is a shared add-on priced at EUR 5/month. AI-assisted document drafting also requires the AI Composer add-on because it uses the shared AI generation path.