Introduction

Automation Editor

7min

The primary build page for Pathfix Automation is the automation editor called Design. You will add, build, edit and modify your automations from the Design page. The editor has a visual UI that works just like any other automation tool, but with a focus on helping you automate API integrations on your platform.



Here is a quick video on how you can use Automation to automate your API integrations:







Navigation Breakdown

The main naviation bar for Pathfix Automation can be accessed from all spage. These open in an easy to access popup that does not take you away from the page you are on, making sure you never break your build momentum.

Document image




Environment

Switch between your Dev and Live environments to view automations that are currently in development or in live. You will always start in the Dev space where you will be able to create, configure and make changes before you move an automation to Live.

APIs page

This is where you would add any custom API that you want to consume, this could be your internal private APIs or the API of an external provider. There are a few pre-built APIs available but we understand that not all APIs for all providers can be added, which makes this the best starting point for building your automation.

Design page

This is where the magic happens - the build. You build your integration using an workflow based visual UI. Call APIs, add conditions, loop through a list, send a response, import/export automation - all of it happens here.

Webhooks page

Pathfix Automation comes with webhooks already set up. Click on the Webhooks tab and select Create. Once you have set it up, the webhooks start listening to any events being triggered for your connected users.

Connections page

Click on the Connections tab and connect your account with external solutions. Once connected, you can add any of the APIs to the provider and build your automation.

Constants page

When building an integration, you may have keys or IDs that you are constantly referring to across multiple automations. This is where Constants come in. Add those keys one-time in Constants and simply point to them whenever you need them. Need to change a Constant? Simple edit the Constant and all the referencing automations will automatically pick this up.

You can also add Constants for separate environments within your application (e.g. staging, development, live, internal etc.).

Monitor page

Monitor the status of your automation tasks by clicking on Monitor in the toolbar. You can view details of the call including time of call, status (success or failure) and details of each tasks run in a simple to use JSON format.









Updated 13 Jun 2023
Doc contributor
Did this page help you?