Connect Langfuse to Easybill

Both apps 28Langfuse 14Easybill 14

• Trigger
  New Trace

  Polling trigger: fires for newly created traces (dedup by trace id / timestamp). GET /api/public/traces

• Action
  Add Comment

  Add a comment to a trace/observation/session/prompt object. POST /api/public/comments

• Action
  Add Dataset

  Create a new dataset. POST /api/public/v2/datasets

• Action
  Add Dataset Item

  Create an item (input/expected_output/metadata) in a dataset. POST /api/public/dataset-items

• Action
  Add Prompt

  Create a new prompt version (text or chat). POST /api/public/v2/prompts

• Action
  Add Score

  Create a score attached to a trace/observation/session (numeric, categorical, or boolean). POST /api/public/scores

• Action
  Delete Trace

  Delete a trace by id. DELETE /api/public/traces/{traceId}

• Action
  Get Project

  Reads the Langfuse project that the connection's project-scoped API key belongs to.

• Action
  Get Prompt

  Get a prompt by name (and optional version/label). GET /api/public/v2/prompts/{promptName}

• Action
  Get Trace

  Get a single trace by id, including nested observations/scores. GET /api/public/traces/{traceId}

• Action
  List Dataset Items

  List items in a dataset. GET /api/public/dataset-items

• Action
  List Datasets

  List all datasets in the project. GET /api/public/v2/datasets

• Action
  List Prompts

  List all prompts in the project. GET /api/public/v2/prompts

• Action
  List Scores

  List scores with optional filters. GET /api/public/v2/scores

• Action
  Add customer

  Create a new customer. POST /customers

• Action
  Add document

  Create a new document (invoice, quote, etc). POST /documents

• Action
  Add project

  Create a new project. POST /projects

• Action
  Add task

  Create a new task. POST /tasks

• Action
  Add time tracking

  Create a new time tracking entry. POST /time-trackings

• Action
  Delete customer

  Delete a customer. DELETE /customers/{id}

• Action
  Delete document

  Delete a document. DELETE /documents/{id}

• Action
  Get customer

  Fetch a single customer by id. GET /customers/{id}

• Action
  Get document

  Fetch a single document by id. GET /documents/{id}

• Action
  List documents

  Fetch a list of documents. GET /documents

• Action
  List projects

  Fetch a list of projects. GET /projects

• Action
  List tasks

  Fetch a list of tasks. GET /tasks

• Action
  Update customer

  Update an existing customer. PUT /customers/{id}

• Action
  Update document

  Update an existing document. PUT /documents/{id}

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.