Skip to main content
The Generate Callback URL action creates a unique, temporary URL that external systems can use to send data back to your workflow. When this action runs, it generates a callback URL. You can optionally include an API key in the URL for authentication. The API key must be a valid Blink key with permission to execute workflows. To leverage this callback URL, it requires to:
  1. send it to external system (e.g. via custom http request)
  2. Add a Wait Action to the following step, to wait for the callback response. Your workflow will pause until the callback request is received. When data is sent to the callback URL, the workflow automatically resumes and continues to the next step, using the data returned by the external system.

Handling Callback Responses in Workflows

After generating a Callback URL using the Generate Callback URL action, immediately after you need to add a wait action to the step step, to pause the workflow execution while the external service completes its process and sends back a request with relevant data upon completion.

Example Use Case

Callback URLs are especially useful in workflows that involve asynchronous interactions with third-party systems. For example, a customer uses blink to automate a support ticket triage:
  • When an end user submits a support request through the customer’s support portal, a blink workflow is triggered to create a corresponding ticket in the external ticketing system (with a callback URL).
  • After creating the ticket, the wait action pauses the workflow, until the ticket is assigned and its SLA is defined on the ticketing system’s side.
  • Once those updates occur, the ticketing system sends the relevant details back to blink using the callback URL.
  • Blink then resumes the workflow and passes the updated ticket information back to the user.
In this scenario, the callback URL enables smooth, secure coordination between blink and the external ticketing platform, allowing the workflow to handle asynchronous operations seamlessly.