ManyRequests integrations: native connections, Zapier and payment gateways

Native integrations versus portal embeds

ManyRequests integrations come in two kinds, and the difference matters. A native integration exchanges data with ManyRequests. A portal integration is an embed: the other tool is shown inside your client portal as an extension, and no data is synced. The vendor's integrations page labels each tool as one or the other.

So the ClickUp and Monday entries do not sync tasks. They put a ClickUp or Monday view in front of the client. If you need requests to become tasks elsewhere, that is a Zapier or webhook job.

Which plan each integration needs

The vendor says there is no cap on how many tools you connect. Third-party tools such as Zapier have their own pricing. The Core vs Pro comparison shows what else the upgrade buys.

What the Zapier connection can trigger and do

Zapier is the main route to tools ManyRequests does not connect to directly, such as a separate CRM, accounting software or a spreadsheet. The help center's trigger and action list, dated April 2026, includes:

• Triggers: client created or updated, organization created, request created, updated or completed, task created or completed, payment created, brand created, team member created, ticket created and canvas comment created.
• Actions: create client, create organization, create brand, create request, update request, update request status, update request credits, create comment, find comments for a request and cancel client subscription.

An older help article lists a slightly different set, including subscription created and subscription canceled triggers. Check the live list inside Zapier before you design an automation around one specific event.

Setting up Zapier, step by step

1. In your ManyRequests portal, open Settings, then Integrations.
2. Copy the API token shown there.
3. In Zapier, start a new Zap and choose ManyRequests as the app.
4. Paste the token when Zapier asks you to connect the account.
5. Pick a trigger, for example Request Created, then add the action in the other app.
6. Submit a test request from a test client account and confirm the Zap ran.

Afterwards, check that the fields you mapped arrive filled in, and that a request update does not fire the same Zap twice. Webhooks are set up in the same Integrations screen on Pro: add a webhook, give it a name, a URL and one event. Seven events are documented, covering clients, requests, payments, comments and subscription cancellations.

Payment gateways: Stripe only

Stripe is the one connected payment gateway. Through it, clients can pay by credit or debit card, Apple Pay and Google Pay when enabled, and ACH bank transfer for US clients. To connect it, go to Modules and Extensions, choose Billing and switch on Connect to Stripe. Trials on recurring services need Stripe connected first.

PayPal, Wise and direct bank transfers are not integrated. You create the invoice, select manual payment and mark it paid yourself once the money arrives. That works for a few custom invoices but not for automated subscription renewals. The payment gateways guide covers this in more depth.

When the integration list is not enough

If you need two-way sync with a project tool, a native accounting connection or PayPal checkout, ManyRequests does not provide it directly. Your options are Zapier, Pro webhooks or the ManyRequests API. Teams that want to keep project work in ClickUp should read ManyRequests vs ClickUp before paying for both.