HI. I am a bit new to Salesforce Automation Flows. Yay for me getting into it :) Great to be here!
Quick question, and I apologise if this is not new to the community, We have a Flow that does a Jira Create Issue action ... we select the Jira Project/space and the relevant Issue/Work item type and want to set the fields ... but there are some fields that do not appear to populate. Eg the Summary field is missing and cant be set in the flow and it is required in Jira. I saw the Jira Create Issue Meta via the API and the front end and the summary is in there ... but Salesforce Flow just doesnt allow me to set it. I clicked Refresh next to "Set Input Values for the Selected Action" and Select Fields and Refresh Fields in the "Manage Jira OAuth Fields" modal but it just cannot find the field. I am noticing this for some other fields and other projects and issue types too. Please advise? Thanks in advance. Yatish
Hi Yatish,
Apologies for the delay — here's the accurate current process (this has actually changed slightly since older guides, so want to make sure you're not following an outdated version).
Setting up the HTTP Callout for Jira's Create Issue API
1. In Flow Builder, add a new Action element, then select "Create HTTP Callout" (this is the current button label — it's built directly into the Action picker now, not something you create separately under Setup first).
2. It'll ask you to set up an External Service. Give it a name (e.g., JiraCreateIssue), and you'll be prompted to select or create a Named Credential + External Credential pair. This is where Jira's auth actually lives — for Jira Cloud, you'll want either:
- API Token auth (Basic auth: your Atlassian email + API token) — simplest to set up, or
- OAuth 2.0 (3LO) if your org already has an Atlassian OAuth app registered
3. Enter the endpoint: POST
https://yourcompany.atlassian.net/rest/api/3/issue4. Salesforce will ask for a sample JSON response to generate the schema. Use something like:
{
"id": "10001",
"key": "PROJ-123",
"self": "
https://yourcompany.atlassian.net/rest/api/3/issue/10001"
}
5. For the request body schema, you'll define the input fields yourself (project key, issuetype id, summary, description, etc.) since this is a POST — Flow lets you build the JSON body structure manually here, which is exactly what gives you the Summary field access that the native connector was hiding from you.
6. Save, then the action becomes available under Action elements in any Flow going forward.
On your OAuth reconnect question
To directly answer it: reconnecting/reauthorizing an existing Jira OAuth connection (the one your native Jira connector already uses) generally just refreshes the token — it doesn't reset field mappings or break other Flows using that same connection, since the connection and the field-mapping metadata are stored separately. That said, since you're setting up a brand-new HTTP Callout action with its own separate Named Credential (as above), you don't actually need to touch the existing Jira OAuth connection at all — this new setup runs independently, so there's zero risk to your other Flows either way.
