Actions
actions
Methods
Create an action. Once an action is created, it must be deployed, and then bound to a trigger before it will be executed as part of a flow.
Example: Authorization: Bearer My Bearer Token
The unique ID of the action.
True if all of an Action's contents have been deployed.
The time when this action was built successfully.
The source code of the action.
The time when this action was created.
The list of third party npm modules, and their versions, that this action depends on.
True if the action should be deployed after creation.
The version of the action that is currently deployed.
installed_integration_id is the fk reference to the InstalledIntegration entity.
Integration defines a self contained functioning unit which partners publish. A partner may create one or many of these integrations.
The name of an action.
The Node runtime. For example: node12, defaults to node12
The list of secrets that are included in an action or a version of an action.
The build status of this action.
The list of triggers that this action supports. At this time, an action can only target a single trigger at a time.
The time when this action was updated.
Deletes an action and all of its associated versions. An action must be unbound from all triggers before it can be deleted.
Deploy an action. Deploying an action will create a new immutable version of the action. If the action is currently bound to a trigger, then the system will begin executing the newly deployed version of the action immediately. Otherwise, the action will only be executed as a part of a flow once it is bound to that flow.
Retrieve all actions.
Retrieve an action by its ID.
Test an action. After updating an action, it can be tested prior to being deployed to ensure it behaves as expected.
Update an existing action. If this action is currently bound to a trigger, updating it will not affect any user flows until the action is deployed.
Domain types
Executions
actions.executions
Methods
Retrieve information about a specific execution of a trigger. Relevant execution IDs will be included in tenant logs generated as part of that authentication flow. Executions will only be stored for 10 days after their creation.
Domain types
The result of a specific execution of a trigger.
Triggers
actions.triggers
Methods
Retrieve the set of triggers currently available within actions. A trigger is an extensibility point to which actions can be bound.
Methods
Retrieve the actions that are bound to a trigger. Once an action is created and deployed, it must be attached (i.e. bound) to a trigger so that it will be executed as part of a flow. The list of actions returned reflects the order in which they will be executed during the appropriate flow.
Update the actions that are bound (i.e. attached) to a trigger. Once an action is created and deployed, it must be attached (i.e. bound) to a trigger so that it will be executed as part of a flow. The order in which the actions are provided will determine the order in which they are executed.
Domain types
Binding is the associative entity joining a trigger, and an action together.
Versions
actions.versions
Methods
Performs the equivalent of a roll-back of an action to an earlier, specified version. Creates a new, deployed action version that is identical to the specified version. If this action is currently bound to a trigger, the system will begin executing the newly-created version immediately.
Retrieve all of an action's versions. An action version is created whenever an action is deployed. An action version is immutable, once created.
Retrieve a specific version of an action. An action version is created whenever an action is deployed. An action version is immutable, once created.
Domain types