Skip to content

Conversation

@NAVIN0507
Copy link

Summary

This PR adds Authorization (Bearer token) support to the Motia Workbench request trigger, allowing developers to test protected APIs that require authentication. The implementation preserves header casing, automatically prefixes Bearer when missing, and safely ignores inactive or invalid headers.

Related Issues

N/A

Type of Change

  • Bug fix
  • [ Y] New feature
  • Breaking change
  • Refactor
  • Other (please describe):

Checklist

  • [ Y] I have read the CONTRIBUTING.md
  • [ Y] My code follows the code style of this project
  • I have added tests where applicable
  • I have tested my changes locally
  • I have linked relevant issues
  • I have added screenshots for UI changes (if applicable)

Screenshots (if applicable)

image ## Additional Context Improves compatibility with common backend authentication middleware

@vercel
Copy link

vercel bot commented Jan 5, 2026

@NAVIN0507 is attempting to deploy a commit to the motia Team on Vercel.

A member of the Team first needs to authorize it.

@NAVIN0507 NAVIN0507 changed the title Feat(workbench) add authorization bearer token support for protected ap is feat(workbench): add authorization bearer token support for protected APIs Jan 5, 2026
@NAVIN0507 NAVIN0507 changed the title feat(workbench): add authorization bearer token support for protected APIs feat : add authorization bearer token support for protected APIs Jan 6, 2026
@anthonyiscoding
Copy link
Contributor

Hey @NAVIN0507, thank you for this contribution! Adding Authorization Bearer token support to the Workbench request trigger is a great feature — being able to test protected APIs directly from the Workbench is something developers will definitely appreciate.

However, I wanted to let you know that we're currently working on a major architecture change that will fundamentally change the internals of how Motia handles request routing, authentication, and API interactions.

Because of the depth of these changes, the dashboards and their request handling will look quite different once the new engine is in place. We'd love for you to revisit this contribution at that point — your understanding of the auth flow and how developers interact with protected APIs will be really valuable in shaping the experience on the new architecture.

I really appreciate you taking the time on this and seeing all your contributions!

Also I may have mentioned this previously but to be the first to know when the architecture change is released please add your email to this form: https://forms.gle/24iCHL9yAk1i6LDc6

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants