Swiftgum Trigger icon

Swiftgum Trigger

Listen for Swiftgum PDF extraction webhooks, filtered by schema. To test, upload a PDF in your Swiftgum workspace — this node will emit the extracted data once processed.

Overview

This node acts as a webhook trigger for Swiftgum, a service that extracts data from PDFs. It listens for incoming webhook events sent by Swiftgum when PDF extraction is completed. Users can filter these events by specific schema IDs or names to only receive relevant extracted data.

Common scenarios include automating workflows that process or analyze data extracted from PDFs uploaded to Swiftgum workspaces. For example, after uploading a PDF invoice to Swiftgum, this node can trigger downstream automation to update accounting records or notify teams.

Properties

Name Meaning
Schema (Optional) Names or IDs Filter incoming webhook events to only those matching selected schemas. Leave empty to receive all events. Options are loaded dynamically from the Swiftgum API and can be chosen by name or ID.

Output

The node outputs JSON data representing the payload received from the Swiftgum webhook. This JSON contains the extracted data from the processed PDF according to the specified schema(s). The output is an array with one element per webhook event.

No binary data is output by this node.

Dependencies

  • Requires an API key credential for authenticating with the Swiftgum API.
  • Needs internet access to communicate with https://app.swiftgum.com/api/v1.
  • The node subscribes to Swiftgum webhooks by registering its own webhook URL with the service.
  • The node verifies webhook authenticity using HMAC SHA256 signatures with a secret provided during subscription.

Troubleshooting

  • Signature Mismatch: If the webhook signature verification fails, the node logs a warning and ignores the request. Ensure the webhook secret is correctly stored and that Swiftgum sends valid signatures.
  • Missing Subscription: If the webhook subscription ID is missing or deleted, the node will attempt to recreate it. Make sure the API key has permissions to manage webhooks.
  • Schema Filtering Issues: If no events are received when filtering by schema, verify that the correct schema IDs or names are selected and that the PDFs uploaded to Swiftgum match those schemas.
  • Network Errors: Failures in subscribing or deleting webhooks may occur due to network issues or invalid credentials. Check API key validity and network connectivity.

Links and References

Discussion