← All integrations
Atlassian
Productivity & documentsJira issues, Confluence pages, and Loom videos.
You connect Atlassian once through its own sign-in screen, and every workflow you build can use it. Malleable never sees your password.
Use it in a workflow
Tell the architect, the AI that builds your workflows, what you want done in your own words. For example:
When a customer reports a bug, open a Jira issue with the details and link it in the support thread.
Access and security
- You grant access on Atlassian's own consent screen, and Malleable stores the resulting token, never your password.
- Every run uses the connection the workflow's owner set up, so anyone who can run the workflow acts with that account's access in Atlassian. Connect an account or key with only the access the workflow needs.
- You can revoke access at any time in Atlassian's settings.
Malleable is SOC 2 Type II certified and doesn't train AI models on your data. More in Security & data handling and our Trust Center.
Connection details for IT
Atlassian's server only accepts sign-ins from AI apps on its allowed list. Before anyone connects, an Atlassian organization admin adds www.usemalleable.com to that list in Atlassian Administration. Atlassian publishes its own MCP server, which workflows connect to at https://mcp.atlassian.com/v2/mcp.