microsoft / microsoft/PowerPlatformConnectors

[SERVICE TEAM SUPPORT REQUEST] Get workflow name in custom connector trigger

Open
#3,668 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
1.3k
Forks
1.5k
Avg merge
5d 15h
Merged PRs (30d)
11

Description

Description of Feature or Work Requested

Hi All 👋

We have a custom connector which contains a webhook trigger. Whenever a someone uses the trigger in their workflow Microsoft power automate will call our service to register the webhook. As part of this webhook registration we will receive a request containing details like the webhook url and the unique identifier for the workflow, however it does not seem to include the name of the workflow. What would be the best way to get the workflow name so that we can display this to users within our own application?

Note that when the same trigger is used in Microsoft Logic apps we do receive the workflow name as part of the request header.

Target Date

ASAP

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the custom connector webhook trigger registration request and the details Power Automate sends, including the webhook URL and workflow identifier. Compare this with the workflow-name header received from Microsoft Logic Apps; done would require a confirmed, supported way to obtain the workflow name in Power Automate or a documented limitation.

Written by the indexing model from the issue text.

Assessment

Domain
api
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
18/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.