List Expenses with Zoho Books API on New Requests (Payload Only) from HTTP / Webhook API

Pipedream makes it easy to connect APIs for Zoho Books, HTTP / Webhook and 2,400+ other apps remarkably fast.

Trigger workflow on

New Requests (Payload Only) from the HTTP / Webhook API

Next, do this

List Expenses with the Zoho Books API

No credit card required

▶

Watch us build a workflow

8 min

Watch now ➜

Trusted by 1,000,000+ developers from startups to Fortune 500 companies

Developers ♥ Pipedream

Getting Started#

This integration creates a workflow with a HTTP / Webhook trigger and Zoho Books action. When you configure and deploy the workflow, it will run on Pipedream's servers 24x7 for free.

Select this integration
Configure the New Requests (Payload Only) trigger
1. Connect your HTTP / Webhook account
Configure the List Expenses action
1. Connect your Zoho Books account
2. Configure organization_id
3. Optional- Configure description
4. Optional- Configure reference_number
5. Optional- Configure date
6. Optional- Select a status
7. Optional- Configure amount
8. Optional- Configure account_name
9. Optional- Configure customer_name
10. Optional- Configure vendor_name
11. Optional- Configure customer_id
12. Optional- Configure vendor_id
13. Optional- Configure recurring_expense_id
14. Optional- Configure paid_through_account_id
15. Optional- Configure search_text
16. Optional- Select a sort_column
17. Optional- Select a filter_by
18. Optional- Configure page
19. Optional- Configure per_page
Deploy the workflow
Send a test event to validate your setup
Turn on the trigger

Details#

This integration uses pre-built, source-available components from Pipedream's GitHub repo. These components are developed by Pipedream and the community, and verified and maintained by Pipedream.

To contribute an update to an existing component or create a new component, create a PR on GitHub. If you're new to Pipedream component development, you can start with quickstarts for trigger span and action development, and then review the component API reference.

Trigger#

New Requests (Payload Only) on HTTP / Webhook

Description:Get a URL and emit the HTTP body as an event on every request

Version:0.1.1

Key:http-new-requests-payload-only

View on GitHub

HTTP / Webhook Overview#

Build, test, and send HTTP requests without code using your Pipedream workflows. The HTTP / Webhook action is a tool to build HTTP requests with a Postman-like graphical interface.

Point and click HTTP requests

Define the target URL, HTTP verb, headers, query parameters, and payload body without writing custom code.

$A screenshot of Pipedream's HTTP Request Configuration interface with a GET request type selected. The request URL is set to 'https://api.openai.com/v1/models'. The 'Auth' tab is highlighted, indicating that authentication is required for this request. In the headers section, there are two headers configured: 'User-Agent' is set to 'pipedream/1', and 'Authorization' is set to 'Bearer {{openai_api_key}}', showing how the OpenAI account's API key is dynamically inserted into the headers to handle authentication automatically.$

Here's an example workflow that uses the HTTP / Webhook action to send an authenticated API request to OpenAI.

Focus on integrating, not authenticating

This action can also use your connected accounts with third-party APIs. Selecting an integrated app will automatically update the request’s headers to authenticate with the app properly, and even inject your token dynamically.

Pipedream integrates with thousands of APIs, but if you can’t find a Pipedream integration simply use Environment Variables in your request headers to authenticate with.

Compatible with no code actions or Node.js and Python

The HTTP/Webhook action exports HTTP response data for use in subsequent workflow steps, enabling easy data transformation, further API calls, database storage, and more.

Response data is available for both coded (Node.js, Python) and no-code steps within your workflow.

Trigger Code#

import http from "../../http.app.mjs";

// Core HTTP component
// Returns a 200 OK response, emits the HTTP payload as an event
export default {
  key: "http-new-requests-payload-only",
  name: "New Requests (Payload Only)",
  // eslint-disable-next-line
  description: "Get a URL and emit the HTTP body as an event on every request",
  version: "0.1.1",
  type: "source",
  props: {
    // eslint-disable-next-line
    httpInterface: {
      type: "$.interface.http",
      customResponse: true,
    },
    http,
  },
  async run(event) {
    const { body } = event;
    this.httpInterface.respond({
      status: 200,
      body,
    });
    // Emit the HTTP payload
    this.$emit({
      body,
    });
  },
};

Trigger Configuration#

This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI and CLI.

Label	Prop	Type	Description
N/A	`httpInterface`	`$.interface.http`	This component uses `$.interface.http` to generate a unique URL when the component is first instantiated. Each request to the URL will trigger the `run()` method of the component.
HTTP / Webhook	`http`	`app`	This component uses the HTTP / Webhook app.

Trigger Authentication#

The HTTP / Webhook API does not require authentication.

About HTTP / Webhook#

Get a unique URL where you can send HTTP or webhook requests

Action#

List Expenses on Zoho Books

Description:List all the Expenses.

Version:0.2.1

Key:zoho_books-list-expenses

View on GitHub

Zoho Books Overview#

Zoho Books API unlocks the potential to automate and streamline accounting tasks by integrating with Pipedream's serverless platform. With this powerful combo, you can automate invoicing, manage your accounts, reconcile bank transactions, and handle contacts and items without manual input. By setting up event-driven workflows, you can ensure data consistency across platforms, trigger notifications, and generate reports, all while saving time and reducing human error.

Action Code#

// legacy_hash_id: a_gnir81
import { axios } from "@pipedream/platform";

export default {
  key: "zoho_books-list-expenses",
  name: "List Expenses",
  description: "List all the Expenses.",
  version: "0.2.1",
  type: "action",
  props: {
    zoho_books: {
      type: "app",
      app: "zoho_books",
    },
    organization_id: {
      type: "string",
      description: "In Zoho Books, your business is termed as an organization. If you have multiple businesses, you simply set each of those up as an individual organization. Each organization is an independent Zoho Books Organization with it's own organization ID, base currency, time zone, language, contacts, reports, etc.\n\nThe parameter `organization_id` should be sent in with every API request to identify the organization.\n\nThe `organization_id` can be obtained from the GET `/organizations` API's JSON response. Alternatively, it can be obtained from the **Manage Organizations** page in the admin console.",
    },
    description: {
      type: "string",
      description: "Search expenses by description.Variants `description_startswith` and `description_contains`. Max-length [100]",
      optional: true,
    },
    reference_number: {
      type: "string",
      description: "Search expenses by reference number. Variants `reference_number_startswith` and `reference_number_contains`. Max-length [100]",
      optional: true,
    },
    date: {
      type: "string",
      description: "Search expenses by expense date. Variants `date_start`, `date_end`, `date_before` and `date_after`. Format [yyyy-mm-dd]",
      optional: true,
    },
    status: {
      type: "string",
      description: "Search expenses by expense status. Allowed Values `unbilled`, `invoiced`, `reimbursed`, `non-billable` and `billable`.",
      optional: true,
      options: [
        "unbilled",
        "invoiced",
        "reimbursed",
        "non-billable",
        "billable",
      ],
    },
    amount: {
      type: "string",
      description: "Search expenses by amount. Variants: `amount_less_than`, `amount_less_equals`, `amount_greater_than` and `amount_greater_than`.",
      optional: true,
    },
    account_name: {
      type: "string",
      description: "Search expenses by expense account name. Variants `account_name_startswith` and `account_name_contains`. Max-length [100",
      optional: true,
    },
    customer_name: {
      type: "string",
      description: "Search expenses by customer name. Variants: `customer_name_startswith` and `customer_name_contains`. Max-length [100]",
      optional: true,
    },
    vendor_name: {
      type: "string",
      description: "Search expenses by vendor name. Variants: `vendor_name_startswith` and `vendor_name_contains`.",
      optional: true,
    },
    customer_id: {
      type: "string",
      description: "ID of the expense account.",
      optional: true,
    },
    vendor_id: {
      type: "string",
      description: "ID of the vendor the expense is made.",
      optional: true,
    },
    recurring_expense_id: {
      type: "string",
      description: "Search expenses by recurring expense id.",
      optional: true,
    },
    paid_through_account_id: {
      type: "string",
      description: "Search expenses by paid through account id.",
      optional: true,
    },
    search_text: {
      type: "string",
      description: "Search expenses by account name or description or `customer name` or `vendor name`. Max-length [100]",
      optional: true,
    },
    sort_column: {
      type: "string",
      description: "Sort expenses.Allowed Values `date`, `account_name`, `total`, `bcy_total`, `reference_number`, `customer_name` and `created_time`.",
      optional: true,
      options: [
        "date",
        "account_name",
        "total",
        "bcy_total",
        "reference_number",
        "customer_name",
        "created_time",
      ],
    },
    filter_by: {
      type: "string",
      description: "Filter expenses by expense status. Allowed Values `Status.All`, `Status.Billable`, `Status.Nonbillable`, `Status.Reimbursed`, `Status.Invoiced` and `Status.Unbilled`.",
      optional: true,
      options: [
        "Status.All",
        "Status.Billable",
        "Status.Nonbillable",
        "Status.Reimbursed",
        "Status.Invoiced",
        "Status.Unbilled",
      ],
    },
    page: {
      type: "string",
      description: "By default first page will be listed. For navigating through `pages`, use the `page` parameter.",
      optional: true,
    },
    per_page: {
      type: "string",
      description: "The `per_page` parameter can be used to set the number of records that you want to receive in response.",
      optional: true,
    },
  },
  async run({ $ }) {
  //See the API docs: https://www.zoho.com/books/api/v3/#Expenses_List_Expenses

    if (!this.organization_id) {
      throw new Error("Must provide organization_id parameters.");
    }

    return await axios($, {
      method: "get",
      url: `https://books.${this.zoho_books.$auth.base_api_uri}/api/v3/expenses?organization_id=${this.organization_id}`,
      headers: {
        Authorization: `Zoho-oauthtoken ${this.zoho_books.$auth.oauth_access_token}`,
      },
      params: {
        description: this.description,
        reference_number: this.reference_number,
        date: this.date,
        status: this.status,
        amount: this.amount,
        account_name: this.account_name,
        customer_name: this.customer_name,
        vendor_name: this.vendor_name,
        customer_id: this.customer_id,
        vendor_id: this.vendor_id,
        recurring_expense_id: this.recurring_expense_id,
        paid_through_account_id: this.paid_through_account_id,
        search_text: this.search_text,
        sort_column: this.sort_column,
        filter_by: this.filter_by,
        page: this.page,
        per_page: this.per_page,
      },
    });
  },
};

Action Configuration#

This component may be configured based on the props defined in the component code. Pipedream automatically prompts for input values in the UI.

Label	Prop	Type	Description
Zoho Books	`zoho_books`	`app`	This component uses the Zoho Books app.
organization_id	`organization_id`	`string`	In Zoho Books, your business is termed as an organization. If you have multiple businesses, you simply set each of those up as an individual organization. Each organization is an independent Zoho Books Organization with it's own organization ID, base currency, time zone, language, contacts, reports, etc. The parameter `organization_id` should be sent in with every API request to identify the organization. The `organization_id` can be obtained from the GET `/organizations` API's JSON response. Alternatively, it can be obtained from the Manage Organizations page in the admin console.
description	`description`	`string`	Search expenses by description.Variants `description_startswith` and `description_contains`. Max-length [100]
reference_number	`reference_number`	`string`	Search expenses by reference number. Variants `reference_number_startswith` and `reference_number_contains`. Max-length [100]
date	`date`	`string`	Search expenses by expense date. Variants `date_start`, `date_end`, `date_before` and `date_after`. Format [yyyy-mm-dd]
status	`status`	`string`	Select a value from the drop down menu:`unbilledinvoicedreimbursednon-billablebillable`
amount	`amount`	`string`	Search expenses by amount. Variants: `amount_less_than`, `amount_less_equals`, `amount_greater_than` and `amount_greater_than`.
account_name	`account_name`	`string`	Search expenses by expense account name. Variants `account_name_startswith` and `account_name_contains`. Max-length [100
customer_name	`customer_name`	`string`	Search expenses by customer name. Variants: `customer_name_startswith` and `customer_name_contains`. Max-length [100]
vendor_name	`vendor_name`	`string`	Search expenses by vendor name. Variants: `vendor_name_startswith` and `vendor_name_contains`.
customer_id	`customer_id`	`string`	ID of the expense account.
vendor_id	`vendor_id`	`string`	ID of the vendor the expense is made.
recurring_expense_id	`recurring_expense_id`	`string`	Search expenses by recurring expense id.
paid_through_account_id	`paid_through_account_id`	`string`	Search expenses by paid through account id.
search_text	`search_text`	`string`	Search expenses by account name or description or `customer name` or `vendor name`. Max-length [100]
sort_column	`sort_column`	`string`	Select a value from the drop down menu:`dateaccount_nametotalbcy_totalreference_numbercustomer_namecreated_time`
filter_by	`filter_by`	`string`	Select a value from the drop down menu:`Status.AllStatus.BillableStatus.NonbillableStatus.ReimbursedStatus.InvoicedStatus.Unbilled`
page	`page`	`string`	By default first page will be listed. For navigating through `pages`, use the `page` parameter.
per_page	`per_page`	`string`	The `per_page` parameter can be used to set the number of records that you want to receive in response.

Action Authentication#

Zoho Books uses OAuth authentication. When you connect your Zoho Books account, Pipedream will open a popup window where you can sign into Zoho Books and grant Pipedream permission to connect to your account. Pipedream securely stores and automatically refreshes the OAuth tokens so you can easily authenticate any Zoho Books API.

Pipedream requests the following authorization scopes when you connect your account:

ZohoBooks.fullaccess.all

About Zoho Books#

Online accounting software

More Ways to Connect Zoho Books + HTTP / Webhook#

Other Popular Integrations#

Create Customer Payment with Zoho Books API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + Zoho Books

Try it

Create Customer Payment with Zoho Books API on New Requests from HTTP / Webhook API

HTTP / Webhook + Zoho Books

Try it

Create Employee with Zoho Books API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + Zoho Books

Try it

Create Employee with Zoho Books API on New Requests from HTTP / Webhook API

HTTP / Webhook + Zoho Books

Try it

Create Invoice with Zoho Books API on New Requests (Payload Only) from HTTP / Webhook API

HTTP / Webhook + Zoho Books

Try it

Popular Triggers#

New Requests from the HTTP / Webhook API

Get a URL and emit the full HTTP event on every request (including headers and query parameters). You can also configure the HTTP response code, body, and more.

Try it

New Requests (Payload Only) from the HTTP / Webhook API

Get a URL and emit the HTTP body as an event on every request

Try it

New event when the content of the URL changes. from the HTTP / Webhook API

Emit new event when the content of the URL changes.

Try it