Create New Automation

before you can create, publish and start using any automation, you will start your build in the dev environment in this environment, you will be able to create a new automation edit an existing automation test your automation run view all logs related to tests done in the dev space once you are done with the build, you can publish your automation to live designing your automation click on design from the toolbar and select create new you can also edit your existing automation by clicking the edit icon from the design popup or from your automation home page endpoint an endpoint is generated for every automation build, this can be used to trigger the automation the endpoint can be triggered from your app or from a webhook the endpoint for the automation is accessible through the properties window of the first task select the first task and click on the properties tab name your automation to save your automation if you have a sample json payload (either sent from your app as part of the endpoint call or received from a webhook), you can enter it under the call data (json) section (note this allows you to pick a response in the following tasks) add a description if you'd like (optional, for internal purpose only) click on other settings and select endpoint to get the endpoint for your automation add api task add tasks to the automation such as api, conditions etc through the add action tab select the task and click on call api (or click on the + icon) to add a new api task to your automation add a title and click on select api search for the api by name or provider (if you don't see the one you want, you can add it through the api editor https //autodocs pathfix com/api editor ) apis are listed under the following categories my apis private apis that have been configured by you/your team direct pre configured apis that call provider apis directly and will use accounts that you ahve connected through the connections tab pathfix oauth apis that are configured to work with your pathfix oauth account for all your connected users core apis that perform core functions in your automation data received (read more on core apis https //autodocs pathfix com/core api functions here) depending on the api selected, you will need to choose the connection to use (if there are no connections, click on add connection and authorise a new connection) complete all requested information to complete the api setup you can choose to add dynamic content to each of the fields from the previous task (this can either be data sent from your app, received from a webhook or any of the previous api call data) you can now proceed to add additional tasks by clicking on the + icon use api response data pathfix automation allows you to use the data received from all your previous api calls in the next api call this means, you can use this data in your next api call see example below, which shows how you can add the xero customer data received in your slack notification you send to your customer/team optional advanced settings each api task added has optional advanced settings that allow you to add a delay between your calls (this is especially useful if the provider api you are accessing has an api limiting in place) run synchronously allows you to wait for the api call to finish (wait for a response from the provider) before moving on to the next api) by default this is set to auto which automatically either waits for a response or moves on to the next api based on which api response is consumed test and enable once you have built your automation and added the apis you want to connect, click on the test and publish tab to run a test against all your api calls in the automation before you can push to live this is a mandatory step the entire automation will execute push to live after testing has been completed successfully on all tasks configured, you can publish your automation by clicking push to live please note, you will not be able to publish an automation without running the test first once published, click on endpoints to copy the live or dev endpoints schedule automation you can choose the automation to run on a schedule (instead of an endpoint trigger), this can be done by changing the schedule type for your automation click on schedule and choose how you would like to trigger this automation manual if you would like to call the endpoint from your app or use webhooks, leave this option as default time select how many minute intervals to run the automation for start at select the data and time to run your automation viewing live automation once you have published your automation to live , you can switch to your live enviroment by clicking on the environment name on the top navigation bar and selecting live here, you can view all live automations view all tasks configured in an automation copy the endpoint of the automation enable or disable an automation you will not be able to change any of the configuration of a live automation to make changes, you will have to switch to your dev environment, make the change, test it and then push to live