Skip to main content

How do I trigger my own code when a document is uploaded?

Enable FormKiQ document events and route the relevant EventBridge event to your integration. Your handler can validate, enrich, notify, or synchronize a document using the authorized API. Document actions also support processing pipelines. Treat delivery as retryable and potentially duplicated, and read current document state before applying a business change.

Select the right trigger​

Use the events reference to select the actual event name and payload for the deployed release. A document-created event and a processing-completed event represent different milestones. If a handler needs OCR text or scan results, sequence it after that processing rather than treating upload completion as readiness.

Configure a rule for the intended environment, source, event type, and site. Route it to a supported EventBridge target such as Lambda or SQS. An arbitrary HTTP endpoint requires the appropriate adapter or EventBridge API destination configuration. FormKiQ intake webhooks receive uploads; they are not automatically outbound change subscriptions.

Make handlers recoverable​

Use stable document/site identifiers and a persisted operation key to make repeated delivery safe. Re-read authoritative metadata when processing an older notification. Bound retries and send exhausted failures to a monitored dead-letter queue.

Test duplicate, delayed, and failed delivery. Reconciliation should repair a missed event without creating another document or repeating a payment, notification, or approval.

Edition and configuration​

Document events and actions are available in Core. A workflow, processor, or external target may require commercial capabilities and separate AWS configuration.

Continue with the detailed guides​

Privacy settings

Analytics is optional. Your analytics choice is shared with formkiq.com and remembered for up to six months. Change it here at any time.

Essential preferences and search

We remember your privacy choice and display preferences. Search runs in your browser using Pagefind files hosted with the docs. It works whether you accept or reject analytics.

Measure page views and installation-link clicks. This does not enable advertising on the docs. Existing marketing choices for the main website are kept unchanged.

Read the docs privacy notice or manage other main-website privacy choices.