Hi, If I create a connect on forge app can the connect part use automationActions modules?
I don’t see why not, but please let us know if something doesn’t work as expected there.
I wasn’t sure if there were connect modules that didn’t work when the two are combined. So for connect on forge apps you can use any connect module at all?
Known incompatibilities are listed here - I don’t know if we’ve specifically tested automationActions but it should work fine and it will quickly be apparent if not.
@paul Do you mean this? https://developer.atlassian.com/cloud/jira/service-desk/automation-action/
If so, do you realize that it is a legacy thing? (If you are, then sorry, but if you aren’t, I wanted to warn you.)
1 Like
@aron.gombas No, I didn’t realise it was legacy. I should have since it was at the top of the page. Thanks for the warning. I was looking for a way to interface with Jira automation using something other than webhooks and thought this was it
@paul Jira Automation cannot be extended with third party actions, still. We are also waiting for that extension possibility.
(I had the feeling that you are looking for that, and I wanted to warn you early so that you don’t waste your time.)
1 Like
Thanks @aron.gombas, I appreciate it. I saw something about using webhooks, in actions, but haven’t found it again. Maybe I’m getting confused with the deprecated.
This topic was automatically closed after 30 days. New replies are no longer allowed.