HumDay

Automate Figshare

HumDay reads Figshare’s own published API description and derives 136 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.

Automate Figshare

What Figshare is

Figshare apiv2. Using Swagger 2.0

API host: api.figshare.com

What HumDay can do in Figshare

73 documented operations change something in Figshare. The 51 most useful are listed here.

What HumDay can read from Figshare

These are the operations a schedule or a trigger can watch.

How automating Figshare works

  1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
  2. Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
  3. See it proven. The program runs and shows you the result before it is allowed near your live Figshare account.
  4. Grant access, then go live. You approve the specific Figshare operations it may use — and only those.

Popular Figshare integrations

Connect Figshare to the tools people pair it with most.

Automate Figshare with these

Categories

Questions about Figshare automation

Can HumDay connect to Figshare?
Yes. HumDay reads Figshare's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 136 operations are documented.
Do I need to write code to automate Figshare?
No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Figshare account.
What can HumDay do in Figshare?
73 of the 136 documented operations change something in Figshare, and 63 read from it. HumDay only ever uses the specific operations your approved contract needs.
Is my Figshare account safe?
Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Figshare is held behind that approval.

Where this came from

The operations above are read from a published API description for Figshare at docs.figshare.com/swagger.json. Descriptions are the provider’s own words, not ours. Last published 2023-03-06.