Integration
Connect Open Science Framework to Octopus Deploy
When New comment fires in Open Science Framework, your agent runs Add project in Octopus Deploy. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Open Science Framework and Octopus Deploy to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Open Science Framework can start in Octopus Deploy
When New comment in Open Science Framework
then Add project in Octopus Deploy
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Open Science Framework and Octopus Deploy
Triggers and actions 3 triggers · 28 actions
- New comment
Polling trigger that fires when a new comment is added to an OSF project.
- New preprint
Polling trigger that fires when a new OSF preprint is created.
- New registration
Polling trigger that fires when a new OSF registration is created.
- Get collection
Retrieve a single OSF collection.
- Get contributor
Retrieve a single contributor on an OSF project.
- Get file
Retrieve metadata for a single OSF file.
- Get preprint
Retrieve a single OSF preprint.
- Get project
Retrieve a single OSF project by id.
- Get registration
Retrieve a single OSF registration.
- Get resource
Retrieve a single OSF outcome resource.
- Get user
Retrieve a single OSF user.
- Get wiki page
Retrieve a single OSF wiki page.
- List comments
List comments on an OSF project.
- List contributors
List the contributors on an OSF project.
- List project files
List the files stored in an OSF project.
- List projects
List OSF projects (nodes) visible to the user.
- List registrations
List OSF registrations.
- List resources
List OSF outcome resources.
- List wiki pages
List the wiki pages on an OSF project.
- Add project
Creates a new project in an Octopus Deploy space, placed in a project group and using a lifecycle.
- Add release
Creates a new release of an Octopus Deploy project with the version number you choose.
- Add runbook
Creates a new runbook in an Octopus Deploy project.
- Get project
Returns a single Octopus Deploy project by its ID or slug.
- Get runbook
Returns a single runbook from an Octopus Deploy space, including its project, published snapshot and settings.
- List deployments
Returns deployments in an Octopus space, optionally filtered to specific environments or projects.
- List deployment targets
Returns the deployment targets (machines) in an Octopus space, optionally filtered by name.
- List environments
Returns the environments in an Octopus Deploy space, optionally filtered by name or ID.
- List projects
Returns the projects in an Octopus Deploy space, optionally filtered by name or ID.
- List releases
Returns the releases in an Octopus Deploy space, optionally filtered by version text or release IDs.
- List tasks
Returns Octopus server tasks (deployments, runbook runs, health checks and other background work), optionally filtered by state.
- List tenants
Returns the tenants in an Octopus space, optionally filtered by name, project or tenant tag.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Open Science Framework
Open Science Framework to TrackingTimeTime Tracking app that helps to manage projects, track working times and measure productivity.
Open Science Framework to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Open Science Framework to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Open Science Framework to Google SheetsGoogle Sheets
Open Science Framework to StripeStripe is a payment processing platform for online businesses.
Open Science Framework to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
More into Octopus Deploy
HubSpot to Octopus DeployHubSpot is your all-in-one stop for all of your marketing software needs.
Gmail to Octopus DeployGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to Octopus DeployGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Open Science Framework and Octopus Deploy, answered
What can start an automation from Open Science Framework?
Any of Open Science Framework's 3 triggers in the catalog, including New comment, New preprint and New registration. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Octopus Deploy when something happens in Open Science Framework?
Any of Octopus Deploy's 12 actions, including Add project, Add release, Add runbook and Get project. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Octopus Deploy to Open Science Framework?
Octopus Deploy has no triggers in the catalog today, so automations start in Open Science Framework. If you need the other direction, ask: your agent reads Octopus Deploy's API documentation and adds it.
Do I have to build a connector for Open Science Framework or Octopus Deploy?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
Can my AI client use Open Science Framework and Octopus Deploy without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.