Does Wisegrid have native integrations like Slack, Teams, or Jira?
Not as built-in connectors yet. Those are on the roadmap (the connector panel has a "request a connector" capture so your interest sets the order). What ships today is outbound webhooks: you point one at any HTTPS endpoint and reach Slack, Teams, Zapier, Make, or your own service in a couple of lines of glue, without waiting on us to build a dedicated connector.
How do I connect Wisegrid to other apps?
Through per-sheet outbound webhooks. On a sheet you can manage (editor or owner), add a webhook with a target URL and the row events it should fire on. From then on, a matching change POSTs a JSON payload to that URL. Anything that can receive an HTTPS POST (Zapier Catch Hook, Make, n8n, a serverless function, your backend) becomes a connection.
Does Wisegrid have webhooks like Smartsheet?
Yes. Wisegrid fires outbound webhooks on row changes. You subscribe each webhook to the events you care about (row created, updated, deleted, or a bulk update), and every matching change sends a signed JSON POST to your endpoint. You can run up to 10 webhooks on a single sheet, each pointed at a different URL with its own event subscription.
Which row events can a Wisegrid webhook fire on?
row.created, row.updated, row.deleted, and rows.bulk_updated. You pick the subset per webhook, so an integration that only cares about new rows never hears about deletes. A bulk paste or bulk edit collapses into one rows.bulk_updated event per sheet, so a large change sends one POST per webhook instead of one POST per row.
How do I verify a webhook actually came from Wisegrid?
Each delivery is signed with HMAC-SHA256 using a per-webhook secret, sent in an X-Wisegrid-Signature: sha256=... header. On your side you recompute the HMAC of the raw request body with the same secret and compare. This is the same pattern Stripe uses for its inbound signatures. The secret is generated when you create the webhook and shown once so you can copy it; the delivery log never echoes it.
Can a webhook point at an internal or localhost URL?
No, and that is deliberate. The target URL is checked against an SSRF guard that blocks private, loopback, and link-local addresses and requires HTTPS. A bad URL is rejected with a clear error before it ever saves. The check runs again at send time against the freshly resolved IP, so a hostname that later re-points at an internal address (a DNS-rebind) is caught and not delivered. Redirects are disabled, since a 302 to an internal host is the classic bypass.
What happens if my webhook endpoint goes down?
A failed delivery retries on a growing backoff: roughly 1 minute, then 5 minutes, 30 minutes, 2 hours, and 6 hours before giving up. The scheduled retries are persisted, so they survive a process restart or a blue/green deploy. After a sustained run of consecutive failures the webhook auto-disables so a dead endpoint stops getting hammered on every row change. Fix it, re-enable it, and the first success resets the failure counter to zero. A 410 Gone disables it immediately, since the receiver is telling you the endpoint is gone for good.
Will a big Smartsheet import flood my webhook with thousands of calls?
No. Import-sourced row events are skipped entirely, so migrating a 10,000-row Smartsheet workspace does not fan out 10,000 POSTs. Your integrations see real, interactive changes (user edits, form submissions, automation writes), not migration noise. The importer is not a webhook trigger.
Can I see whether a webhook actually delivered?
Yes. Each webhook has its own delivery log. For every attempt it records the event, whether it succeeded, the HTTP status code, a short diagnostic on failure, the attempt count, and the next scheduled retry time while it is still retrying. The log is safe to share with teammates: it has no column for the signing secret or the target URL, so it cannot leak either.
What does the webhook payload contain, and does it include personal data?
The JSON body carries the event name, the sheet and row ids, the change source, a delivery timestamp, the row version, and the cell values before and after the change. For the person who made the edit it includes their display name only. It never includes their email address or user id, the same name-only rule the activity log follows.
How is Wisegrid Connections different from Smartsheet integrations?
Smartsheet leads with a catalog of prebuilt connectors. Wisegrid leads with a signed, hardened outbound webhook you control, so you are not blocked waiting for a specific connector to exist. You get HMAC signing, an SSRF guard rechecked at send, automatic retries with backoff, auto-disable on dead endpoints, and a per-webhook delivery log out of the box. Native connectors are being added on top of that foundation, with the order driven by what users request.
Do I need to write code to use connections?
You need an endpoint that can receive an HTTPS POST. If you already use Zapier, Make, or n8n, their generic webhook trigger gives you that with no code, and you build the rest of the flow visually. If you run your own service, you add a small route that verifies the X-Wisegrid-Signature header and reads the JSON body. Either way, setup on the Wisegrid side is just a URL plus the events you want.