Integrations

Slot VG·Sign into your stack.

Post envelope events to a Slack or Microsoft Teams channel, or send signed JSON to any HTTPS address, including Zapier, Make and n8n. All of it is set up in Settings, under Integrations.

On this page

Webhook endpoints are managed by the workspace owner in Settings, Integrations, on every plan. A workspace can have up to 10 endpoints. The API token on the same page needs Pro, Team or Enterprise; see API & developers.

Slack

  1. In Slack, open Apps, then Incoming Webhooks, click Add to Slack, pick a channel and copy the URL Slack gives you.
  2. In VG·Sign, under Webhook endpoints, click Add endpoint and choose Slack.
  3. Paste the URL into Endpoint URL. It has to be a hooks.slack.com address. Name (optional) helps you tell endpoints apart.
  4. Tick the events you want, click Save endpoint, then click Send test. The test goes out within a minute.

Each message names the event and the envelope, and links to its audit trail in VG·Sign.

Microsoft Teams

  1. In Teams, open Workflows and choose “Post to a channel when a webhook request is received”. Power Automate gives you a URL.
  2. In VG·Sign, click Add endpoint and choose Microsoft Teams.
  3. Paste the URL. It has to be the flow address on logic.azure.com; government tenants on logic.azure.us are not accepted.
  4. Tick your events, click Save endpoint and Send test.

VG·Sign sends an Adaptive Card, which the flow posts to the channel.

Webhooks

Choose HTTPS endpoint to receive the events in your own system.

  • The URL must use https and be reachable from the internet. Local and private network addresses are refused.
  • There are 19 event types in three groups: Envelope lifecycle, Recipient activity and Identity. A new endpoint starts with Sent to recipients, Completed, Declined and Voided ticked. Events marked Frequent can fire many times for one envelope.
  • After you save, the secret appears under Signing secret, shown once. Copy it then. Rotate secret issues a new one.
  • Each delivery is a JSON POST with an X-VG-Signature header, sha256= followed by an HMAC-SHA256 of the raw body keyed with that secret, and an X-VG-Delivery-Id header that stays the same across retries.
  • A failed delivery is tried up to 3 times, then marked failed. The last five deliveries are listed under each endpoint, and a failed one has a Resend button. Pause stops deliveries without deleting the endpoint.

The payload is documented on the Webhooks page.

Zapier, Make and n8n

These tools connect through a webhook: each one can start a workflow from a catch-hook URL, which VG·Sign treats like any other HTTPS endpoint.

  1. In Zapier, Make or n8n, start a workflow with a webhook trigger and copy its URL.
  2. In VG·Sign, click Add endpoint, keep HTTPS endpoint, paste the URL and tick your events.
  3. Click Save endpoint, then Send test to post a sample ping event to the new URL.

Back to help center

  • Build with the same primitives we use.

    The VG·Sign REST API creates, sends and tracks envelopes with a workspace token. It is included on Pro, Team and Enterprise, and the full reference is on the API page.

    Read
  • Build once, send forever.

    A template keeps an envelope’s documents, field layout and signing roles. Fill in names and emails to start a new envelope from it, or send one envelope for every row of a CSV file.

    Read