pipefy-members-email-webhooks

Members, Email & Webhooks

MCP clients: read references/mcp.md. CLI users: read references/cli.md. Examples below describe shared operation arguments.

Manage pipe membership, send emails from card inboxes, read inbox replies, and manage webhooks.

---

Member management

Operation	Read-only	Purpose
invite_members	No	Invite one or more users by email + role.
add_service_account_to_pipe	No	Attach an existing org service account to a pipe by email + role (iPaaS setup). Check membership afterwards.
remove_member_from_pipe	No	Destructive; review and approve first. Check afterwards: org-level permissions can override pipe removal.
set_role	No	Change a member's pipe role (member_id = user id).

List existing members with get_pipe_members from pipefy-pipes-and-cards. Id forms: docs/mcp/tools/identifiers.md#members-email-webhooks.

Steps — invite members

1. Check existing members:

   Operation: get_pipe_members(pipe_id=67890)

2. Invite new members:

   Operation: invite_members(pipe_id=67890, members='[{"email":"[email protected]","role_name":"member"},{"email":"[email protected]","role_name":"admin"}]')

   Before inviting external emails (domain different from the org's known domains), warn the user that this is an external invitation and confirm before proceeding.

   Before granting admin role, confirm with the user — admin is the highest pipe-level role.

Steps — add a service account to a pipe (iPaaS setup)

When setting up an iPaaS (Advanced Automations) flow that runs under a service account, the account must be a member of the target pipe, or pipe-scoped calls under its identity fail with a permission error even though the flow looks configured.

1. Get the service account's email. Either create one with create_service_account(organization_uuid, name, role) — which returns the account's email plus its OAuth2 client secret and token endpoint once (store them immediately) — or take the email from your organization's service-account settings. A freshly created account has no pipe access until this step. The pipe role defaults to admin (a service account running automations usually needs full pipe access); pass a narrower role only when you deliberately want to limit it.