Skip to content

Suggested workflows for the caller

GET /automation/examples

What the New workflow box suggests: a curated catalog filtered to the apps THIS caller can actually use (a connection they own or that was shared with them, active, and not blocked for them by a restriction), backfilled with examples that need no app. Never names an app the caller cannot see a connection to. Each row carries a ready-to-send `prompt`, a short `label` and the `apps` it joins with the connector catalog's own name and logo. Paged like every list; the order is the order to offer them in.

Response Body

next_cursorstring,null
prev_cursorstring,null
resultobject[]
appsobject[]
3 properties
logostring,null
namestring
slugstring
idstring
labelstring
promptstring
curl -X GET 'https://api.elaichi.ai/automation/examples' \
  -H 'Authorization: Bearer $ELAICHI_API_TOKEN' \
  -H 'Content-Type: application/json'
const response = await fetch('https://api.elaichi.ai/automation/examples', {
  method: 'GET',
  headers: {
    'Authorization': 'Bearer ' + process.env.ELAICHI_API_TOKEN,
    'Content-Type': 'application/json',
  },
});

const data = await response.json();
console.log(data);
import os
import requests

url = "https://api.elaichi.ai/automation/examples"
headers = {
    "Authorization": f"Bearer {os.environ['ELAICHI_API_TOKEN']}",
    "Content-Type": "application/json",
}

response = requests.get(url, headers=headers)
print(response.json())