TriggerAgencyHandyReal-timeUpdated June 2026

When does AgencyHandy fire on payment failures?

Short answer: In TinyCommand, add the AgencyHandy Payment Failed trigger to a workflow and publish. It listens through a AgencyHandy webhook and fires your workflow within seconds of the event, with no polling and no code. Add a filter if you only want some events to start a run.

Use this trigger All 14 AgencyHandy triggers

Anatomy

What this trigger looks like in a workflow.

Drop it on the canvas. Configure a couple of fields. Publish.

In the builder

Trigger

Payment Failed

When the matching event happens

payment failedagencyhandy payment failed

What this trigger returns

for the curious

You don’t need to read this. TinyCommand auto-maps every field into the visual picker so downstream nodes can pull values by clicking. We show it here for power users who want to know what’s on the wire.

{
  "data": {
    "_id": "abc123",
    "timestamp": "2026-04-18T10:00:00Z"
  },
  "event": "payment.failed"
}

Output shape

Fields available to downstream nodes.

Every field below can be referenced by name in any action or filter that comes after this trigger.

Field	Type	Example
data	object	{ … }
data._id	string	"abc123"
data.timestamp	string	"2026-04-18T10:00:00Z"
event	string	"payment.failed"

Pairs with

Drop these actions after Payment Failed.

Add Labels to Message

Gmail · Email

Add Reaction

Slack · Communication

Add Sheet Tab

Google Sheets · Spreadsheets & Databases

Create Company

HubSpot · CRM & Sales

FAQ

Questions about Payment Failed.

How does the Payment Failed trigger work in AgencyHandy?

Fires when a client's payment attempt fails — card declined, insufficient funds, expired card, or gateway error. Payload includes the failure reason where available. The standard dunning hook: trigger the friendly reminder email, mark the project as at-risk, page the account owner if it's a large account.

Is the Payment Failed trigger real-time?

Yes. Payment Failed uses webhooks or push subscriptions, not polling. Your workflow fires within seconds of the event happening in AgencyHandy.

What data does Payment Failed return?

The full event payload from AgencyHandy. The output shape table on this page lists every field, its type, and an example value so you can map fields into downstream nodes.

Can I filter Payment Failed so only some events start a workflow?

Yes. Add a Filter node right after the trigger and match on any field, whether that's subject, sender, status, or anything else in the payload. Workflows only continue when the filter passes.

Do I need AgencyHandy admin permissions to use Payment Failed?

For most AgencyHandy accounts a standard user can authorize the trigger. Some AgencyHandy plans require an admin to enable third-party webhooks. Check AgencyHandy's docs if the trigger fails to register.

More triggers

Other AgencyHandy triggers.

Trigger

Client Created

Fires when a new client is added to AgencyHandy — manually by the agency owner, via API, or through the public client-portal signup. The base hook for agency onboarding automations: kick off the welcome sequence, provision the client portal, create the kick-off project in PM tooling.

Trigger

Invoice Status Changed

Fires whenever an invoice transitions state — draft to sent, sent to viewed, sent to paid, or to overdue. Payload includes the old and new status. The hook for dunning workflows (auto-nudge on overdue), revenue-recognition workflows (sync paid invoices to accounting), and client-state automations.

Trigger

Order Created

Fires when a client places a new order through the AgencyHandy storefront or portal. Payload includes the line items, the client, the total, and any custom fields the order form captured. Use it to kick off fulfillment workflows — auto-create the project, assign to the right team, send the kick-off questionnaire.

Trigger

Order Updated

Fires on any change to an existing order — status transition, scope edit, line-item change, or assignee swap. For workflows that only care about specific transitions (e.g., moved to "Ready for Delivery"), inspect the status field in the payload and short-circuit when it doesn't match.

Trigger

Payment Received

Fires when a payment lands successfully against an invoice or order. Payload includes the amount, currency, payment method, and the invoice/order it cleared. The hook for revenue-tracking workflows (push to QuickBooks/Xero), thank-you automations, and any "client is now paid" downstream state transitions.