Get payments in Figma
A documented Figma operation that only reads, so it can watch for changes without altering anything. Describe what you want to happen and HumDay builds it.
What this operation does
Get payments
- GETReads data · Payments
api.figma.com/v1/payments
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Figma operations the program may use, and this is one of them.
- You approve access. Read-only access is still yours to grant, and still limited to what the contract needs.
Other Figma operations
- Add a comment to a filePOST · changes data
- Create a webhookPOST · changes data
- Add a reaction to a commentPOST · changes data
- Delete a commentDELETE · changes data
- Create dev resourcesPOST · changes data
- Create/modify/delete variablesPOST · changes data
- Delete a reactionDELETE · changes data
- Delete a webhookDELETE · changes data
Questions
- Can HumDay get payments in Figma?
- Yes. This operation is published in Figma's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Does this change anything in my Figma account?
- No. This is a read-only operation, so it can be used to watch for changes or fetch data without altering anything in Figma.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Figma account.
Where this came from
Read from the API description Figma publishes themselves at raw.githubusercontent.com/figma/rest-api-spec/main/openapi/openapi.yaml. The description above is the provider’s own wording, not ours.