How to Send Jira Forms Links to Slack for external submissions

[#1]

When teams work together across tools, even the simplest processes can break down. Take something as basic as sharing a form out of Jira.

Let’s say your team wants to collect structured requests from people who don’t use Jira—whether that’s employees from another department, vendors, clients, or field teams. They need a way to submit information, but you don’t want them navigating Jira, and you definitely don’t want to manage endless back-and-forth chats or copy-pasted messages.

You’ve built a Smart Form that can create new issues automatically. But how do you get that form in front of the right people, in the right moment?

Here’s where Slack comes in. It’s often the central communication hub across teams—even for those who aren’t inside Jira. With Jira Automation and Smart Forms, you can automatically post a form link into a Slack channel the moment a trigger is met: a high-priority request is logged, a release is approaching, or a cross-functional team needs to weigh in.

Anyone in that Slack channel—whether they use Jira or not—can click the form link, fill it out, and submit it. Behind the scenes, a new Jira issue is created with all the mapped fields, attachments, and context you need.

Making Smart Forms Talk to Slack

Smart Forms for Jira allows you to create powerful, flexible forms that live inside Jira issues. They can be added automatically based on issue type or added manually when needed. Once added, each form generates a unique URL—tied to the specific Jira issue it was created for. These links are stored in Jira issue properties, where Jira Automation can access them using smart values.

This means you can configure Jira to detect when a certain condition is met—like a bug being created or a ticket reaching a “Resolved” status—and then pull the right form link and deliver it to a Slack channel using a webhook.

You don’t need custom code. No plugins, no middleware. Just Smart Forms, Jira Automation, and a standard Slack webhook.

Forms can also be configured to allow submissions from external users—no Jira account required. This makes it easy to collect input from customers, contractors, or stakeholders outside your organization. You can control whether users are anonymous or verified, pre-fill form values based on the issue, and even have the form responses update the issue fields automatically.

---

What You’ll Need to Set It Up

To get started, you’ll need a few things in place:

• Smart Forms for Jira installed and configured

• A Slack channel set up with an incoming webhook

• Jira Automation enabled in your project

• A form attached to a test issue

• The right permissions to create and run automation rules

Once these pieces are in place, you're ready to create your rule.

What You Need to Set This Up

To make this work, you’ll need:

• Smart Forms for Jira installed and configured in your site

• A form that’s set to “Create new work item” on submission

• A Slack workspace with an incoming webhook set up

• Jira Automation access to configure the rule

• Proper permissions to post web requests via automation

Your form should be tested, with all the necessary fields mapped to the target issue type in Jira. Once it's ready,add form to work item and the sharable url will become avaliable to Automation Rule, which will be automatically distributed to Slack when the time is right.

---

How to Set It Up: Step-by-Step

Configure the Smart Form

Open your form in Smart Forms and set the submission type to Create Work Item. Choose the correct project and issue type the form will create. Then configure your form with all necessary fields—text fields, dropdowns, attachments, etc.—and apply conditional logic if needed.

By default public sharing is enabled, but if it was turned off, please ensure the public URL is avaliable. This ensures anyone in Slack can access it, even without a Jira account.

Test the form by submitting it yourself. Verify that a new issue is created in the right project with all field mappings applied.

2.1 How Smart Forms Generate Shareable URLs

Smart Forms can automatically generate unique URLs when attached to a Jira issue—either manually or via auto-attach rules. These URLs are saved in issue properties and can be retrieved using smart values in Jira Automation.

You can use this structure:

{{#issue.properties."saasjet.forms.formsSharedUrls"}} {{#if(equals(formName, "Your Form Name"))}}{{url}}{{/}} {{/}}

🔐 Security Note:

• Forms with user picker fields default to “Verified in instance”

• URLs can be regenerated or deactivated anytime

---

Create a Slack Webhook

In your Slack workspace:

1. Search for Incoming Webhooks in Slack

2. Choose the Slack channel you want to post to (e.g., #new-requests, #vendor-access, #onboarding)

3. Slack will generate a Webhook URL—copy this for later use

---

Create the Jira Automation Rule

1. Go to Project Settings → Automation

2. Choose a trigger. For example:

   • “Scheduled” if you want to send the form link every Monday morning

   • “Issue created” if the form should be shared when a specific issue type is logged (e.g., New Hire, Incident)

   • “Status changed” if the form should go out when something is marked “Ready for input”

3. Add any necessary conditions:

   • Check for specific labels, issue types, or projects

   • Example: Only trigger if issue type = “Release Kickoff”

4. Add the Send Web Request action:

   • Method: POST

   • Webhook URL: paste your Slack webhook

   • Header: Content-Type: application/json

   • { "New issue {{issue.key}} – {{issue.summary}} needs attention.",, "attachments": [ { "color": "#36a64f", "fields": [ { "title": "Submit a Request", "value": \{{#issue.properties."saasjet.forms.formsSharedUrls"}}
{{#if(equals(formName, "QA Assessment"))}}{{url}}{{/}}
{{/}}, "short": false } ] } ] }

Replace the value with your form’s name You can customize the message or even add dynamic elements like dates or project names using Jira smart values.

---

Use Cases That Bring This to Life

New Hire Workflows

When an issue of type “New Hire” is created in your HR project, the automation posts a form to #hr-onboarding. That form collects structured onboarding info from team leads, department heads, or the hiring manager. The submission creates a new “Onboarding Task” in Jira and keeps everything traceable.

Vendor Access Requests

Before contractors can access tools, IT or legal needs to collect key information. A weekly scheduled automation posts a form to #vendor-support, prompting managers to fill in vendor names, justification, and access needs. Each submission creates a tracked Jira issue and kicks off approval workflows.

Marketing Intake

When a product enters pre-launch, a “Release” issue is created in the marketing project. That triggers a form link in #marketing-requests, asking content, design, and social teams to submit campaign needs. The form routes all submissions into a shared Jira board, where nothing falls through the cracks.

Incident Post-Mortems

After an incident is marked resolved, a form link posts in #incident-response, allowing stakeholders to fill in impact assessments. Each submission creates a structured follow-up issue tagged to the right service or team, building a searchable record of incident responses.

---

Expanding with Advanced Logic

This automation doesn’t have to be static. You can route different forms to different channels, use smart values to personalize messages, and even chain multiple forms for multi-step workflows.

You can use conditional logic in your form itself to tailor sections based on the department, urgency, or request type. You can also restrict who can edit, view, or resubmit the form—ensuring security without compromising ease of access.

And when forms are submitted, your internal Jira workflow doesn’t miss a beat. Fields are updated, statuses change, SLAs start, and the submission becomes part of your issue lifecycle instantly.

---

Why It Matters

Without this setup, teams rely on scattered requests—Slack pings, emails, DMs. The intake is chaotic. Context gets lost. Follow-ups slip through the cracks.

By sending structured, standardized forms directly to Slack, you align intake with how people already work—without compromising on structure, traceability, or automation. Slack becomes a quiet assistant, delivering exactly the right form at exactly the right time.

No more chasing. No more missed requests. Just clean, trackable, actionable input—from Slack to Jira, in one click.