PipedreamHQ / PipedreamHQ/pipedream
[ACTIONS] Trolley - Add core actions for recipient and payout workflows
- Dominant language
- JavaScript
- Stars
- 11.7k
- Forks
- 5.8k
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 102
Description
**Is there a specific app this action is for?**
Trolley
### Batch and payment processing
[Batches](https://docs.trolley.com/api/#tag/Batches) — Create batch, Retrieve batch summary, Process batch
[Payments](https://docs.trolley.com/api/#tag/Payments) — Create payment, Retrieve payment
### Invoice management
[Invoices](https://docs.trolley.com/api/#tag/Invoices) — Create invoice, Search invoices, Create invoice payment
### Account monitoring
[Balances](https://docs.trolley.com/api/#tag/Balances) — Retrieve all balances
[Verifications](https://docs.trolley.com/api/#tag/Verifications) — List verifications
## Agent/LLM optimization
- **Static schema only** — no `additionalProps`, `reloadProps`, or async option lookups that depend on a parent prop's value. Agents can't resolve multi-step prop chains.
- **Prop descriptions should be directive** — tell the LLM what value to pass and where to get it. For ID inputs, reference the related list/search action (e.g. "Use `List
Recipients` to find a recipient ID by name").
- **Accept human-readable identifiers where supported** — email, name, external ID. Resolve to internal IDs server-side rather than forcing the agent to chain calls.
- **Return the full object** on writes, not just a success boolean or ID. Agents reference return values in downstream steps.
Contributor guide
Assessment
This issue has not been assessed yet.