For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Postman
PricingEnterprise
Contact SalesSign InSign Up for Free
HomeDocs
HomeDocs
      • Overview
        • Overview
          • Blocks reference
            • Action blocks overview
            • Connector
            • HTTP Request
            • Flow
        • Deployed flows overview
        • Connector blocks overview
Postman API Platform

Product

  • Postman Overview
  • Enterprise
  • Spec Hub
  • Flows
  • Agent Mode
  • API Catalog
  • Fern
  • Postman CLI
  • Integrations
  • Workspaces
  • Plans and pricing

API Network

  • App Security
  • Artificial Intelligence
  • Communication
  • Data Analytics
  • Database
  • Developer Productivity
  • DevOps
  • Ecommerce
  • eSignature
  • Financial Services
  • Payments
  • Travel

Resources

  • Postman Docs
  • Academy
  • Community
  • Templates
  • Intergalactic
  • Videos
  • MCP Servers

Legal and Security

  • Legal Terms Hub
  • Terms of Service
  • Postman Product Terms
  • Security
  • Website Terms of Use

Company

  • About
  • Careers and culture
  • Contact us
  • Partner program
  • Customer stories
  • Student programs
  • Press and media
Twitter iconLinkedIn iconGithub iconYouTube iconInstagram iconDiscord icon
Download Postman
Privacy Policy

© 2026 Postman, Inc.

On this page
  • Inputs
  • Outputs
  • Setup
Postman FlowsFlows referenceBlocksActions

Connector blocks

||View as Markdown|
Was this page helpful?
Previous

Action blocks overview

Next

The HTTP Request block

Built with

Connector blocks enable flows in Postman Flows to interact with supported third-party services like Calendly and Figma. There’s a dedicated Connector block for each supported app, with app-specific operations to choose from. For example, the Connector block for Figma has an operation that gets all the comments from a Figma file.

A Connector block consumes two credits each time it runs. To learn more, see How Flows consume credits.

Inputs

Connector block inputs vary depending on the app and the selected operation. For example, for the Figma Connector block’s Get a File by ID operation, there is a File ID input that accepts a string. For the Calendly Get Available Times for Event Type operation, there are three inputs that accept the Event Type, Start Time, and End Time strings.

Outputs

Connector blocks have a Result output that sends the result of the selected operation.

Setup

A new Connector block has two fields: Operation and Account. Under Account, click Connect to connect a new account to the block. If you’ve already connected one or more accounts, click Select an account to select one.

Click Select an operation… to open a dropdown list of operations. Operations are predefined tasks the Connector block can perform with its app. Different operations have different required and optional inputs. When you select an operation and its associated inputs appear, you can provide data for the required inputs from other blocks’ outputs or inserted data blocks.

To learn more, see Connect third-party services to Flows.