Hello Community Scott from Automation Platform here. Today, I am excited to announce a new Automation trigger for Compass now available in both Jira and Confluence Cloud Automation. This also marks our first cross-product trigger, which means you can now initiate a rule from a different product than the one where it is being run.
The trigger will run your rule whenever a component is created in Compass.
In the rule builder, select the “Component created in Compass” trigger:
To use this trigger, you’ll need to have access to a Compass site because you'll need to create a connection:
Once the connection has been created, continue building your rule as normal:
The following Smart Values can be used in actions and conditions to reference the component that triggers your rule:
{{component.name}}
- Prints the name of the Compass component.
{{component.id}}
- Prints the ID of the Compass component.
{{component.url}}
- Prints the URL of the Compass component.
{{component.cloudId}}
- Prints the Cloud ID of the component
{{component.type}}
- Prints the component type.
We’ll be adding more smart values over time, so if there are other Compass data you’d like to use in your Automation rules, leave us a comment below.
We're introducing two new templates to help you get started with Automation for Compass. A new template will be available in both Jira and Confluence.
In Jira, the new template will generate a new issue upon the creation of a component in Compass. This can be used to begin handling component onboarding tasks.
Meanwhile, over on Confluence, the template will publish a new page with the component name as its title. Use this to start creating a runbook for your new component.
The trigger is available right now in Jira and Confluence Cloud!
This is just the start of our exploration into cross-product automation. We value your input on what you expect from automating Compass or any other cross-product workflows you wish to have enabled. Please don't hesitate to schedule time with us directly here or leave a comment on this post
Scott Bell
3 comments