Sign inStart your trial

HarvestHarvest
01Integration field card

Harvest Integration & Invoice Workflow Automation

Run Harvest on autopilot. Keep the veto.

57 actions

Invoice payments get created, projects get deleted, and expense records get updated before you've had a chance to check what fired. Rills proposes every Harvest action; you approve before anything goes out.

Try the approval demo

Interactive. No signup. 14 days free · approvals always free.

Powered by Composio
02. The trust layer

Most automation fires first, asks later. Rills shows you the change before it ships.

Every consequential payments action from Harvest arrives on your phone first. Approve in seconds. Decline without explaining yourself. Workflows wait, paused at zero cost, until you decide.

Queue 3

HARVEST · INVOICE PAYMENT
82

Log 3 invoice payments totalling $4,200 in Harvest?

3 invoices marked overdue · all past 30d

Matching payments confirmed in connected payments tool

Same batch pattern as last month's reconciliation run

SWIPE → APPROVE
Illustrative. Your real proposals match your data and your approval history.
  1. Free to wait. Free to think.

    Approvals and logic don't cost a credit. Pause a workflow for three hours or three weeks. The price is the same: zero. You only pay when something real happens: an AI call, an outbound action.

  2. Approve from your phone in five seconds.

    Swipe right when you're sure. Decline when you're not. Between meetings, mid-coffee, on the train. No dashboard to babysit, no inbox triage, no 3am stomach-drop wondering what shipped while you slept.

  3. Routine cases graduate themselves.

    Every approval feeds a confidence score for that exact workflow shape. The obvious cases (the ones you've green-lit fifty times) start running on their own. The judgment calls still come to you.

03. Overview

About Harvest automation

Billing mistakes in Harvest do not stay inside Harvest. An invoice message sent to the wrong client, a project deleted while hours are still being logged, an expense updated with the wrong category — these go out and then you deal with them.

When Harvest runs unsupervised

Automation that writes directly to your Harvest account can compound a small error into a client-facing problem before you see the first signal.

  • A Create Invoice Message fires to a client whose payment dispute is still open, making your position harder to defend.
  • A Delete Project runs on a project that still has unbilled time attached, and those hours disappear from your records.
  • A Create Expense posts under the wrong expense category, corrupting the report your accountant is about to pull.
  • An Update Task marks billable hours as non-billable across an entire project, silently shrinking your next invoice.
  • A Create Invoice Payment logs a duplicate payment against an invoice that was already settled, throwing your books off.

What Rills does inside Harvest

Rills sits between your workflow logic and your Harvest account. When a rule says to create an invoice payment, delete a client, or send an invoice message, Rills surfaces the proposal with the context it gathered, then waits. Nothing posts to Harvest until you approve Harvest actions explicitly.

The invoice still goes out; you just see exactly what it says before it does.

Why Harvest has no triggers and how Rills fills the gap

Harvest does not emit events that can start a workflow on their own. Rills compensates by running scheduled polls and accepting upstream signals from the tools that do fire events, feeding the results into Harvest operations on a schedule you control.

  • Scheduled invoice review: Rills polls List Invoices on a cadence you set, flags overdue or unsent invoices, and proposes a Create Invoice Message for each one before anything sends.
  • Expense reconciliation: A nightly poll against List Expense Categories and Update Expense catches miscategorized entries and queues corrections for your review each morning.
  • Project hygiene: Rills checks List Clients and Delete Project candidates on a weekly schedule, surfacing stale projects that match your criteria so you decide what closes.
  • Payments automation: When an upstream payments tool confirms a charge, Rills proposes a Create Invoice Payment in Harvest, matched to the right invoice, holding it in queue until you confirm the match is correct.
04. Actions

What Rills can do in Harvest

6 of 57 actions across reads, writes, and updates.

  1. 01

    Create Client

    Register a new client in Harvest to track billable work and manage projects associated with that client. This helps you organize your customer information and set up proper accounting records.

  2. 02

    List Clients

    Retrieve all your clients from Harvest in a paginated list, allowing you to view and manage your customer base. This helps you quickly access client information for invoicing, project assignment, or business reporting.

  3. 03

    Create Estimate

    Create a formal estimate to send to clients for approval before starting work, helping you lock in project scope and pricing upfront.

  4. 04

    Create Expense

    Record and track project-related expenses by creating new expense entries in your accounting system. Use this to log costs like materials, travel, or vendor payments against specific projects for accurate financial tracking.

  5. 05

    Create Invoice

    Create a new invoice in Harvest to bill your clients for completed work or services. This generates an official invoice record that you can send to customers for payment.

  6. 06

    List Invoices

    Retrieve a filtered list of your invoices by client, project, date range, or payment status to track billing activity and cash flow.

05. FAQ

Common questions about Harvest automation

06. NEXT MOVE

Approve every Harvest change before it ships.

14 days free. No credit card. About 90 seconds to your first proposal.