Workflow Apps
Workflow Apps are Whippy's Zapier-style connectors. Each app wraps a third-party API (Slack, Google Sheets, an ATS, an email provider, and many more) so you can use it as a step in the workflow builder.
When a workflow runs, Whippy calls the app for you. You choose the action, map fields from earlier steps, and pick which connected account to use. You don't write HTTP requests or host anything yourself for apps that Whippy (or a partner) already published.
What you can do with an app
Every Workflow App exposes one or more of these step kinds:
| Kind | Role in a workflow |
|---|---|
| Trigger | Starts a workflow when something happens in the other product (for example, a new form submission). Triggers are webhook-based. |
| Search | Looks up or lists records. Searches also power the dropdowns you see when configuring later steps. |
| Create | Changes state in the other product: create, update, delete, or send. |
| Hydrator | Lazily downloads a file when a later step needs it. You don't add hydrators as steps yourself; they run behind the scenes when a file field is mapped. |
Two ways to work with Workflow Apps
| Audience | Start here |
|---|---|
| Everyone in Whippy — connect accounts and use apps as workflow steps | Connect and manage apps · Use apps in workflows |
| Developers and partners — build a custom app with the CLI | Build with the CLI |
Global apps (built by Whippy or a partner and published for every organization) show up in the Auth library and in the workflow step picker. Custom apps you push with the CLI appear for your organization only, until someone with access runs ww-cli make-global to promote them.
Workflow Apps vs other Whippy integrations
Whippy has more than one kind of "integration":
- Workflow Apps (this section) — steps inside the visual workflow builder. Manage connections under Workflows → Auth.
- Settings → Integrations — native ATS/CRM sync (Bullhorn, Avionte, and similar). Those are a different product surface and are not configured with
ww-cli. - REST API, webhooks, and MCP — general-purpose developer access to Whippy data. See Getting started.