Bring Hookdeck Event Gateway into
the flow of work.
A little less busywork with Hookdeck Event Gateway.
Attempt2 capabilities+
- Get an attempt
Retrieve a delivery attempt
- Get many attempts
Retrieve many delivery attempts
Connection6 capabilities+
- Delete a connection
- Get a connection
Retrieve a connection
- Count connections
Count connections without listing them
- Get many connections
Retrieve many connections
- Pause a connection
Hold delivery and queue events
- Unpause a connection
Resume delivery of queued events
Destination3 capabilities+
- Get a destination
Retrieve a destination
- Count destinations
Count destinations without listing them
- Get many destinations
Retrieve many destinations
Event6 capabilities+
- Cancel an event
Stop retrying an event
- Get an event
Retrieve an event
- Count events
Count events up to a limit, since Hookdeck exposes no exact event count
- Get many events
Retrieve many events
- Mute an event
Mute a failed event
- Retry an event
Retry delivery of an event
Issue5 capabilities+
- Dismiss an issue
Ignore an issue
- Get an issue
Retrieve an issue
- Count issues
Count issues without listing them
- Get many issues
Retrieve many issues
- Update an issue
Change the status of an issue
Request3 capabilities+
- Get a request
Retrieve an ingested request
- Get many requests
Retrieve many ingested requests
- Retry a request
Create new events from a request
Source5 capabilities+
- Get a source
Retrieve a source
- Count sources
Count sources without listing them
- Get many sources
Retrieve many sources
- Get or create a source
Return the source with this name, creating it if it does not exist, and give back its public URL. Safe to re-run, and never overwrites an existing source.
- Get the URL of a source
Retrieve the public URL to give a provider
Frequently asked
questions.
What could an Ambacti integration do with Hookdeck Event Gateway?
The documented operations include Attempt: Get an attempt; Attempt: Get many attempts; Connection: Delete a connection; Connection: Get a connection.
Could I keep a workflow read-only?
For a read-only workflow, limit account permissions to reading data and exclude actions that create, update, or delete records.
Will every action run automatically?
Choose which steps could run on their own and which should pause for review. Changes should follow the permissions and approval rules you set.
Do I need to review actions in Hookdeck Event Gateway?
Decide which work could run on its own and which steps need your review.