How-to | Deploy an API service from the Automation node on Dataiku Cloud#

API services can be deployed from the Automation node. This can be useful if, for example, you want an API endpoint to look-up in a dataset that is updated by a Flow running on the Automation node.

  1. Create your API service in the Design node project.

  2. Publish your project to the Automation node. (This tutorial walks through the steps).

  3. Once on the Automation node, build the Flow so as to populate all datasets with data.


    To make sure the Flow on the Design node and the Automation node do not collide and provoke data inconsistencies, your datasets must be relocatable or you must remap the connection on the Automation node.

    If you are using the referenced mode with a dataset in the api-node-referenced-data connection, that dataset will be automatically relocatable; there is nothing for you to do.

  4. Still on the Automation node project on the Automation node, go to the API Designer. Find the API service, and deploy it to the Deployer (click on the service > Publish on Deployer). The endpoints in the service will use the data created by the Automation node Flow.


To have clear naming of all your services, the trick here is when deploying the service to the Deployer to click on the advance option and change the default name of the target service to make it clear it comes from the Automation node (otherwise it will just be suffixed with 2).

Dataiku screenshot of overriding name of target service

If you had also deployed the API service from the project on the Design node, you will have both your Design and Automation API services deployed looking like this:

Dataiku screenshot of 2 deployed API services from Design and Automation node