Skip to content
Explore integrations

mittwald API integration researchA little less busywork with mittwald API.

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 mittwald API workflows with Grunt. Documented operations include Project: Create a project on a server; Project: Create an SFTP user; Project: Create an SSH user. 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.

mittwald API
“Explore whether a Grunt integration could create a project on a server, then create an sftp user in mittwald API. Show me the result and wait for my approval before changing anything.”
A workflow idea to explore.

Illustrative steps and outcome; no real work is performed here.

  1. 01Project: Create a project on a server
  2. 02Project: Create an SFTP user
  3. 03Review the result before anything changes

A clearer next step, with the final say still yours.

Explore possibilities with mittwald API.

Researched operations, not a list of enabled Grunt actions. Actual support, account permissions, supplier terms, and live acceptance require separate verification.

58 researched capabilities across 9 groups

  • Create a project on a server

    Create a new project on a server

  • Create an SFTP user

    Create an SFTP user for a project

  • Create an SSH user

    Create an SSH user for a project

  • Delete an SFTP user

    Delete an SFTP user by ID

  • Delete an SSH user

    Delete an SSH user by ID

  • Delete a project

    Delete an existing project

  • Get a project

    Get details of a specific project

  • Get an SFTP user

    Get details of a specific SFTP user

  • Get an SSH user

    Get details of a specific SSH user

  • Get storage statistics

    Get storage usage statistics for a project

  • List all memberships

    Get a list of all project memberships

  • List all SFTP users

    Get a list of all SFTP users in a project

  • List all SSH users

    Get a list of all SSH users in a project

  • List all projects

    Get a list of all projects

  • List all invites

    Get a list of all project invitations

  • Delete a project membership

    Remove a member from a project

  • Get a project membership

    Get details of a specific project membership

  • Accept an invite to a project

    Accept a project invitation using an invitation token

  • Create an invite to a project

    Create a project invitation

  • Update storage notification threshold

    Update the storage notification threshold of a project

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.

  1. 01

    Start with a small, useful task.

    Describe a routine step involving mittwald API. Keep a first version easy to review and change.

  2. 02

    Plan the account access.

    Check which mittwald API account, data, and permissions a safe connection would need. Start with the least access that can do the job.

  3. 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.

  4. 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 mittwald API?

The documented operations include Project: Create a project on a server; Project: Create an SFTP user; Project: Create an SSH user; Project: Delete an SFTP user. 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 mittwald API 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 mittwald API?

A future integration should let you decide which work could run on its own and which steps need your review.

There’s a Grunt for that

A little less busywork.
A little more you.

Read the current prelaunch status and confirmed prices.

View pricing status Explore the simulation