Currents integration researchA little less busywork with Currents.
Research only. Grunt is prelaunch, live service is paused, and live provider connections and outcomes remain unverified. The operations and examples below are not confirmed live Grunt features or approved supplier commitments.
Explore possible Currents workflows with Grunt. Documented operations include Action: Get many actions; Action: Get an action; Instance: Get an instance. Actions on this page are research candidates from public integration definitions, not confirmation that Grunt support is live.
Exploratory scope only: these candidates come from public integration definitions and are not confirmed as live Grunt features.
Currents
“Explore whether a Grunt integration could get many actions, then create an action in Currents. Show me the result and wait for my approval before changing anything.”
Illustrative steps and outcome; no real work is performed here.
- 01Action: Get many actions
- 02Action: Create an action
- 03Review the result before anything changes
A clearer next step, with the final say still yours.
Explore possibilities with Currents.
Researched operations, not a list of enabled Grunt actions. Actual support, account permissions, supplier terms, and live acceptance require separate verification.
26 researched capabilities across 9 groups
- Get many actionsRead
Get many actions for a project
- Get an actionRead
Get a single action by ID
- Create an actionWrite
Create a new action for a project
- Delete an actionWrite
Archive an action (soft delete)
- Disable an actionWrite
Deactivate an active action
- Enable an actionWrite
Reactivate a disabled action
- Update an actionWrite
Update an existing action
Proposed setup considerations
The research notes below describe a possible setup. They are not instructions for an available Grunt connection; actual steps depend on supported operations and provider approval.
- 01
Start with a small, useful task.
Describe a routine step involving Currents. Keep a first version easy to review and change.
- 02
Plan the account access.
Check which Currents account, data, and permissions a safe connection would need. Start with the least access that can do the job.
- 03
Test the details together.
Validate a sample against a disposable account. Confirm which records are read, what could change, and how errors or duplicates are handled.
- 04
Keep the say-so.
Decide which steps could run on their own and which would need your review. Expand access only when the workflow needs it.
RESEARCH NOTES
Questions about the concept.
These notes describe possible uses. Customer availability remains unverified.
What could a Grunt integration do with Currents?
The documented operations include Action: Get many actions; Action: Get an action; Instance: Get an instance; Project: Get project insights. These are research candidates from public integration definitions and need validation and Grunt implementation before they can be treated as supported capabilities.
Could I keep a workflow read-only?
The research candidates do not confirm an implemented Currents connection or a read-only access mode. If built, verify least-privilege scopes and reject writes at the app API boundary.
Will every action run automatically?
If a connection is built, choose which steps could run on their own and which should pause for review. Changes should follow the permissions and approval rules you set.
Do I need to review actions in Currents?
A future integration should let you decide which work could run on its own and which steps need your review.
A little less busywork.
A little more you.
Read the current prelaunch status and confirmed prices.
View pricing status Explore the simulation