Automate Google Workflow Executions
HumDay reads Google Workflow Executions’s own published API description and derives 4 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.
What Google Workflow Executions is
Execute workflows created with Workflows API.
API host: workflowexecutions.googleapis.com
What HumDay can do in Google Workflow Executions
2 documented operations change something in Google Workflow Executions.
- POSTCreates a new execution using the latest revision of the given workflow.
/v1beta/{parent}/executions - POSTCancels an execution of the given name.
/v1beta/{name}:cancel
What HumDay can read from Google Workflow Executions
These are the operations a schedule or a trigger can watch.
- GETReturns a list of executions which belong to the workflow with the given name.
/v1beta/{parent}/executions - GETReturns an execution of the given name.
/v1beta/{name}
How automating Google Workflow Executions works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- 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.
- See it proven. The program runs and shows you the result before it is allowed near your live Google Workflow Executions account.
- Grant access, then go live. You approve the specific Google Workflow Executions operations it may use — and only those.
Automate Google Workflow Executions with these
- Gmail79 operations
- Google+9 operations
- Google Abusive Experience Report2 operations
- Google Accelerated Mobile Pages (AMP) URL1 operations
- Google Access Approval7 operations
- Google Access Context Manager9 operations
- Google ACME DNS2 operations
- Google Ad Exchange Buyer38 operations
- Google Ad Exchange Buyer II50 operations
- Google Ad Experience Report2 operations
- Google Admin SDK122 operations
- Google AdMob7 operations
Categories
Questions about Google Workflow Executions automation
- Can HumDay connect to Google Workflow Executions?
- Yes. HumDay reads Google Workflow Executions's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 4 operations are documented.
- Do I need to write code to automate Google Workflow Executions?
- 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 Google Workflow Executions account.
- What can HumDay do in Google Workflow Executions?
- 2 of the 4 documented operations change something in Google Workflow Executions, and 2 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Google Workflow Executions 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 Google Workflow Executions is held behind that approval.
Where this came from
The operations above are read from a published API description for Google Workflow Executions at workflowexecutions.googleapis.com/$discovery/rest?version=v1beta. Descriptions are the provider’s own words, not ours. Last published 2023-04-21.