← Xoolink

Xoolink integration recipes beta

Four paths connect Xoolink to an organization's usual stack. Slack and Yousign are native connections. HubSpot and Notion use a controlled recipe: read-only Xoolink API, signed webhook, then a server-side or automation relay.

A recipe is not direct access to your target account. Never paste a HubSpot or Notion key into Xoolink. Keep each platform's secrets in the vault of your server or automation relay.

Slack · native connection

  1. In the organization's admin dashboard, click View connection.
  2. Choose Connect Slack, authorize Xoolink and select a channel.
  3. Use Test in the destination list to confirm delivery.

Xoolink does not keep the Slack OAuth token. Only the channel destination is encrypted. See the Slack and webhooks guide.

HubSpot · CRM recipe

  1. Click Prepare the recipe. Xoolink preselects the three read permissions and the six public cycles.
  2. Create the Xoolink key and put it in your relay's vault. It is used to re-read the current public state after a signal.
  3. Expose an HTTPS URL that verifies the Xoolink signature, deduplicates on X-Xoolink-Event-Id, then writes to HubSpot with your own HubSpot integration's permissions.
  4. Paste only that HTTPS URL into Xoolink. Keep the standard JSON format.
Reconciliation keydata.id

Keep this Xoolink identifier in a dedicated property so you update the same record instead of duplicating it.

Suggested fieldstype · title · status · url

Add the summary, expertise, date, location and last update depending on the CRM object you choose.

Create / updateneed.created · need.updated · event.created · event.updated

Upsert by external identifier, then re-read the resource through the API if your mapping needs the full current state.

Withdrawal / cancellationneed.withdrawn · event.cancelled

Move the record to withdrawn or cancelled. Do not recreate content that is no longer public.

Notion · watch-list recipe

  1. Click Prepare the recipe, then create a time-limited Xoolink key.
  2. In Notion, prepare a database shared with your integration, containing at minimum a unique Xoolink identifier.
  3. Your relay verifies the webhook, looks up a row by external identifier, then creates or updates that row.
  4. Paste the relay's HTTPS URL into the Xoolink webhook form and send a test.
Minimum propertiesXoolink ID · Name · Type · Status · URL

The identifier prevents duplicates; the URL keeps the Xoolink page as the source of truth.

Useful propertiesExpertise · Date · Location · Updated

These fields make a filterable watch list without copying any private data.

Yousign · native connection

Yousign comes in after a Xoolink pact has been consented to and sealed. The admin connects the organization's account; signers then receive their personal link. See the electronic signature guide.

Order of going live

  1. Start with a test environment and a 30- or 90-day Xoolink key.
  2. Verify the signature before parsing or writing the data.
  3. Answer 2xx quickly, process in a queue afterwards, and make every write idempotent.
  4. Test creation, update, withdrawal and cancellation before switching on the real flow.
  5. Watch the Xoolink delivery log and rotate any exposed secret.