Support Ticket Created: AgencyHandy trigger

Anatomy

What this trigger looks like in a workflow.

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

In the builder

Trigger

Support Ticket Created

When the matching event happens

ticket createdagencyhandy ticket created

What this trigger returns

for the curious

You don’t need to read this. Tiny Command 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": "ticket.created"
}

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	"ticket.created"

FAQ

Questions about Support Ticket Created.

How does the Support Ticket Created trigger work in AgencyHandy?

Fires when a client opens a support ticket through the AgencyHandy client portal. Payload includes the client, the project context, the message, and any priority flag. Route to the right team channel based on project, or auto-assign based on subject-line keyword matching.

Is the Support Ticket Created trigger real-time?

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

What data does Support Ticket Created 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 Support Ticket Created 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 Support Ticket Created?

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 Failed

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.

When does AgencyHandy fire on new client tickets?

What this trigger looks like in a workflow.

Fields available to downstream nodes.

Drop these actions after Support Ticket Created.

Questions about Support Ticket Created.

Other AgencyHandy triggers.

Build a workflow on this trigger.