Skip to main content

Reflect action progress

Once you execute a self-service action, an actionRun object will be created in Port.

This page will teach you how to use Port's API to obtain existing action runs and update them with additional metadata and information about the run. You can use this interaction to mark actions as completed or failed, and keep a consistent history of executed actions and their status.

Where to find your action runs

You can find your existing action runs using one of the following methods:

  • Go to the audit logs page of your portal, then select the Runs tab.
    This page will display all action runs that have been executed in your organization.

  • Go the entity page of your desired Entity, then select the Runs tab.
    This page will display all action runs that have been executed for the selected Entity.

  • Once you have at least one in-progress action run, a panel will be displayed on the right side of the page, showing the runs that are currently in progress.

  • After executing an action from the UI, a toast will appear in the top of the page, with a link to the newly created action run.

Interacting with action runs

Once an actionRun is created, it will have a unique runId. Using this id, you can interact with the action run using Port's API.

Obtain a run's id

How to obtain the runId of an action by method:

The runId will be shown in top-left corner of the action run page:

Get a run's details

You can obtain the details of an action run by making a GET request to the{run_id} endpoint, where {run_id} is the id of the action run.

You will receive a response that looks like this:

"ok": true,
"run": {
"id": "r_QOz6WoOB1Q2lmhZZ",
"status": "IN_PROGRESS",
"blueprint": {
"identifier": "microservice",
"title": "Service"
"action": "create_microservice",
"endedAt": null,
"source": "UI",
"relatedEntityExists": false,
"relatedBlueprintExists": true,
"properties": {
"name": "my-microservice",
"region": "eu-west-1"
"createdAt": "2023-12-07T12:53:52.916Z",
"updatedAt": "2023-12-07T12:53:52.916Z",
"createdBy": "auth0|638879fa62c686d381b36ecb",
"updatedBy": "auth0|638879fa62c686d381b36ecb"

Update a run

You can use Port's API to update an the following properties of an action run:

  • status - The status of the action run. Initial value is IN_PROGRESS, can be set to SUCCESS or FAILURE.
  • statusLabel - A custom message used to add information to the status of the action run.
  • logs - Log entries that will be displayed in the action run's page in Port.
  • summary - A summary of the action run, which will be displayed in the run's page in Port.
Auto-update status

When using a Github workflow as the action backend, a Report workflow status option will be available and set to Yes by default. When using this option, Port will automatically update the status of the action run to SUCCESS or FAILURE according to the result of the Github workflow, so no manual update is required.

When using a Webhook as the action backend, a Request type option will be available. When set to sync, Port will automatically update the status of the action run according to the HTTP response code.

Run details

By sending a PATCH request to the{run_id} endpoint, you can do the following:

  1. Update the run's status, by using the status key with one of these values: SUCCESS, FAILURE.
    This will mark the run as completed and show a visual indicator, for example:

  2. Update the run's status label, by using the statusLabel key with a custom message.
    If a label and a status are both provided, the custom message will be displayed with the status' color. For example, the following request body:

    "status": "FAILURE",
    "statusLabel": "Wrong personal token provided"

    will display the following status label:

    When providing a label only, the status will remain as IN_PROGRESS and the label will be displayed with its neutral color.

  3. Add links to external logs of the job runners, by using the link key - AWS Cloudwatch logs, Github Workflow job, Jenkins job, etc.

Multiple and partial updates

You can make a PATCH request to the endpoint as many times as you need until the action run has finished (as long as you don't terminate the run by changing the status).

Note that every patch request will override the previous information that was available for a given key. For example, when updating the link key multiple times, only the last provided value will be displayed in the action run.

Run logs

By sending a POST request to the{run_id}/logs endpoint, you can do the following:

  1. Add log entries to the run's log, by using the message key.
  2. Update the run's status via the terminationStatus key with one of these values: SUCCESS, FAILURE.
  3. Update the run's status label, by using the statusLabel key.

For example, let's update our action run log with the following POST request body:

"message": "my new log message"

Back in Port, the new log message will be displayed in the action run's page:

If we want to add a final log entry and also mark the action run as successful, we can use the following request body:

"message": "my new log message with final status",
"terminationStatus": "SUCCESS",
"statusLabel": "Completed successfully!"

A log message with the terminationStatus key can only be sent once for an action run. After it is sent, the run status is marked accordingly and the run can no longer be modified.

Tying Entities to an action run

You can also add additional context and metadata to an action run by attaching a run_id query parameter to every API route that creates or changes an Entity (i.e. POST, PUT, PATCH and DELETE requests to the{blueprint_id}/entities/{entity_id} route).

By adding the run_id parameter, you reflect the change made to the Entity as part of the set of steps the action run performed during its runtime.


Tying Entities to an action run is only possible when an action run is in the IN_PROGRESS status.

For example, say you send a POST request to create a new entity, and add your run_id as a query parameter. An example python function that achieves this may look like this:

Python create entity example (click to expand)
def create_entity():
headers = {
'Authorization': 'Bearer [YOUR_ACCESS_TOKEN]'

query = {
"run_id": "[RUN_ID]",
"upsert": "true"

body = {
"identifier": "[ENTITY_IDENTIFIER]",
"title": "[ENTITY_TITLE]",

entity_resp ="[TARGET_BLUEPRINT_ID]/entities", headers=headers, params=query, json=body)
return entity_resp.json()['entity']['identifier']

Now when you look at the action run page in Port, you will see the new Entity listed under the Affected Entities tab:

Multiple entities

It is possible to create, update or delete multiple entities as part of the steps taken by a single action run, and all of these changes will be reflected in the action run page.

Action run JSON structure

The action run object created after executing an action resides under the port_payload key, and has the following structure:

actionThe action's unique identifier.create_microservice
resourceTypeThe resource type that triggered the action. In the case of action runs, it always defaults to
statusThe action's status. In the case of action runs, it always defaults to TRIGGERED.TRIGGERED
triggerAudit data for the action run.Example below
contextContains the context of the action, and has keys for blueprint, entity and runId.Example below
payloadExplanation below.Example below

Example Trigger

The trigger includes audit data such as who triggered the action, and when and how it was triggered (UI or API):

"trigger": {
"by": {
"userId": "auth0|<USER>",
"orgId": "<ORG>",
"user": {
"email": "<USER_EMAIL>",
"firstName": "<USER_FIRST_NAME>",
"lastName": "<USER_LASTT_NAME",
"id": "<USER_ID>"
"at": "2022-07-27T17:50:58.776Z",
"origin": "UI"

Example context

"context": {
"entity": null,
"blueprint": "k8sCluster",
"runId": "r_AtbOjbe45GNDElcQ"

Self-Service Action run payload

The payload object contains the data of the action invocation, it includes the following keys:

  • entity - The entity this run is executed on (in the case of CREATE actions, this will be null).
  • action - The triggered action's configuration, including userInputs, description, etc.
  • properties - This key includes the values provided by the user when executing the action. The keys in this object match the keys defined under the userInputs key in the action definition.

Here is an example payload object for a CREATE action:

"payload": {
"entity": null,
"properties": {
"region": "prod-2-use1",
"title": "dev-env",
"version": "1.2",
"type": "EKS"
Create vs Day-2 actions

An action run of a day-2 action is very similar to that of a create action, with one main difference:
Since day-2 actions are always tied to an entity, the entity itself is also provided in the action run object, under the payload.entity key.