Tokens, webhooks, integrations and settings

These sections exist on every intake.

Tokens. A Public Intake Key is browser-safe and lets an embedded form submit; a Private API Token is for server-side access with chosen scopes. Give the token a name, optionally an expiry, and click Generate Token. The token is shown once; copy it immediately. Revoke stops a token.

Webhooks. Send each submission to your own systems. Add a name, an Endpoint URL, the Events to send (submissions, and for booking intakes every booking event such as created, confirmed, rescheduled, cancelled, completed and no-show), how many retries to attempt, and optional authentication (basic auth or a custom header). Every webhook has a signing secret; the delivery log on each webhook shows every attempt with its result. Webhooks can be paused, enabled and deleted.

Integrations. When your manager has configured them instance-wide, switch them on per intake:

• GVenta Help Desk creates a ticket for every valid submission, with a Ticket source label for filtering in the help desk.
• Mage Mailer adds every submitter to a chosen Contact list. Map your form's fields to the contact's email (required), name, company, job title, phone and website. A list marked "drip campaign" enrols the submitter in that sequence at once.

Settings.

• Email notifications. Email the recipients you list on every valid submission, with a subject template and a reply-to taken from a form field. Send test email checks delivery.
• Spam controls. A hidden honeypot field, a minimum submit time, a duplicate window, and blocked email domains and IP addresses. Spam is kept but not counted.
• Rate limiting per IP, and Retention, which deletes submissions after a number of days.

Delete Intake permanently removes the intake and all its submissions or bookings.