ArticleSubmission.news’s custom triggers allow IT administrators to build more flexible, event-driven automation by triggering workflows from external systems like Jira. without manual intervention.
By integrating Jira with ArticleSubmission.news, IT teams can track user onboarding and offboarding across Jira tickets and trigger workflows based on conditions like ticket creation, moving a ticket to a specific status, and more.
Today we’ll take a deep dive into how to add a custom trigger to an existing Jira integration (Jira Service Management and Jira Software). You can set up custom triggers in existing ones Action-only integrations. If you haven’t yet integrated Jira with ArticleSubmission.news, see this article for instructions on integrating Jira with ArticleSubmission.news.
(FOR A TIP: Custom triggers are not limited to Jira; They can also be activated for platforms such as Zendesk, Freshservice and PagerDuty. You can learn more about custom triggers here.)
Why integrate Jira with ArticleSubmission.news?
Jira’s integration with ArticleSubmission.news enables IT teams to:
- Automate onboarding and offboarding workflows from Jira tickets
- Trigger workflows when an issue is created, updated, or moved to a specific state
- Pass ticket data (user email, username, department, issue key, etc.) directly to ArticleSubmission.news workflows
- Reduce human error by enforcing required data before automation runs
This approach moves automation earlier in the IT workflow lifecycle, before manual work begins.
Step 1: Create a custom trigger in ArticleSubmission.news
Access the integration
Go to Integrations > InstalledFind your existing Jira integration and click Adjust.
Navigate to the Extensions menu and select Get Started.
Select “Create workflow triggers” and then click “Next.”
Name your custom trigger and optionally give it a description. Then click “Next: Incoming Request”.
Important: Copy that Incoming request URL. You use this URL when configuring Jira Automation.
Step 2: Configure Jira to call ArticleSubmission.news
Create a Jira rule
Navigate to the Jira project where you want to trigger the workflow and navigate to “Automation” under the project settings.
Select the “Automations” tab on the right and create a project rule.
Select the criteria that should trigger your workflow. Common examples of this include creating or transitioning an issue to a new state. For this example, we select “Issue Created” and click “Save”.
From the Add Component menu, choose New Action.
Scroll down to the Notifications section and select Send Web Request as the action type.
Paste the ArticleSubmission.news trigger URL into the Webhook URL field in JIRA and change the HTTP method to POST.
For the webhook body, select either “Custom Data” or “Issue Data”. This example uses “custom data” but provides all the data points to be passed from the ticket to ArticleSubmission.news using JIRA Smart Values. The data should follow standard JSON format.
Test your JIRA rule by selecting the “Validate your webhook configuration” drop-down menu and providing a sample problem. Jira then retrieves the selected fields from this issue and sends them to ArticleSubmission.news.
(Pro tip: If you include the issue key in your request, you can use it to write back to the ticket as part of your workflow.)
If your test was successful, click Save and go back to app.articlesubmission.com. If your test was unsuccessful, make sure you followed the steps above correctly.
Step 3: Configure the custom trigger in ArticleSubmission.news
If the above steps were successful, ArticleSubmission.news will show the test as received. Click Next: Configure Workflow Options.
Click the View Raw Data Response field to view the format of the data sent to ArticleSubmission.news.
Select the target of your custom trigger. Typically, a username or email address makes sense in this target field. The easiest way to think about {target} is: “My workflow just ran on {target}.”
Choose whether to expose parameters as if conditions or dynamic fields in the workflow by selecting the check box next to the parameter. See our Custom Triggers article for a list of caveats related to If conditions and dynamic fields.
For any data points that should be required to trigger the workflow, click the parameter and check the “Input is required” checkbox. If a trigger that is missing a required field is sent to ArticleSubmission.news, it will be rejected and an audit log will be created.
Why require fields? For example, if a ticket is missing a user’s name, it’s easier to detect missing data in advance than to run a full workflow of actions and have them all fail because a critical data point is missing.
After configuring your parameters, save and publish your custom trigger and go to the workflow builder to start using your trigger!
Step 4: Build and test your workflow
Once you’ve created a workflow around this new custom trigger, you can start running a full test. Before you begin, make sure your Jira rule is enabled in Jira and your ArticleSubmission.news workflow is published. Then navigate to your Jira board and trigger the evaluation criteria you specified (create new issue, create transition and issue, etc.) and watch your new automation come to life.
What’s next?
If you are a ArticleSubmission.news customer with the Platform API, custom triggers are available to you.
Additional customization within the ArticleSubmission.news API can support custom triggers, custom actions, and push events.
PS: Custom triggers were a topic from a previous InFlight session! Check out the recording here.
Don’t know InFlight? InFlight is a monthly customer-exclusive livestream series that dives deeper into ArticleSubmission.news. You can watch all videos here. (as well as register for the next one!)
ArticleSubmission.news is a leader SaaS Management Platform (SMP)and helps leading IT organizations discover, manage and secure their SaaS applications. To find out more, Request a demo.
