Integrations: guides & tutorials

Claude Marketplace is Anthropic’s limited-preview enterprise program: organizations with an existing Anthropic spend commitment can use part of that commitment to pay for Claude-powered solutions from Anthropic's partners. The official marketplace page lists launch partners including Augment Code, Bolt, CodeRabbit, GitLab, Harvey, Hebbia, Legora, Lovable, Replit, Rogo, and Snowflake. That is not the same as the broader Claude partner network (cloud marketplaces, services firms, and "powered by Claude" listings), which is about ecosystem reach, not commitment-backed buying through Anthropic.

For this story alongside other enterprise AI headlines, see Top 10 AI and tech stories this week (March 17–24, 2026).

Make.com (formerly Integromat) is a strong no-code automation platform with a visual canvas, but it is not the right tool for every team. Its pricing scales on operations — not tasks — which catches many users off-guard. Its learning curve is steeper than Zapier's, and its self-hosted option is non-existent.

If you are reconsidering Make.com, here are the 8 best alternatives to evaluate in 2026, ranked by use case.

Yes, you can build your own Make.com app. If the service you need isn't in Make's library of 1,000+ apps, the Custom Apps tool lets you define your own modules, map them to any REST API, handle authentication, transform data with IML, and publish the result for your team or the broader Make community. Custom apps give you full control over the API surface — something no pre-built module can match for niche or internal services.

This guide walks through the full process: from opening the Apps Editor to shipping a working custom module backed by a real API call.

Production Make.com scenarios fail silently—a transient API timeout at 2 AM stops your entire data pipeline and you only notice at 9 AM when someone asks why the CRM is stale. Every scenario without proper error handling is one network blip away from permanent data loss.

This guide covers every error handling primitive Make.com provides: error routes, the five error directives, retry configuration, incomplete executions, and defensive patterns for building automation that survives real-world failures.

The Make.com HTTP module lets you call any REST API directly from your scenario — no dedicated connector needed. If an app exposes an HTTP endpoint, the HTTP module reaches it. GET, POST, PUT, DELETE, file downloads, OAuth handshakes, and paginated data dumps are all first-class operations.

This tutorial covers every HTTP module variant, walks through request configuration in detail, and finishes with three production-ready examples that show exactly how the module behaves under real-world conditions.

When you pull data from an API in Make.com, you usually get an array — a list of 50 products, 200 contacts, or 100 scraped web pages. The scenario receives that list as one bundle, and most modules can only handle one item at a time.

The Iterator splits that one bundle into N individual bundles. The Aggregator collects them back into one. Master these two modules and you can process any collection in Make.com — loop through rows, transform each item, and ship the results wherever you need.

Notion is the go-to knowledge base for teams. Make.com is the no-code automation platform that connects it to everything else. Together, they let you build workflows that create pages, update databases, sync meeting notes, and push task assignments to Slack—all without writing a single line of code.

This tutorial walks you through the Make.com Notion integration from scratch: connecting the module, building your first scenario, and wiring up a full end-to-end workflow.

Most Make.com scenarios work fine as a straight line: trigger → action → action. But real automation breaks down the moment you need to handle more than one outcome. A lead arrives from LinkedIn — that's a different workflow than one from your contact form. An order is marked "refunded" — that's not the same path as "fulfilled".

Make.com Routers and Filters are the mechanism for adding conditional logic to your scenarios. A Router splits execution into multiple parallel branches. A Filter controls whether a branch runs at all. Together they replace manual if-else thinking with explicit, visual decision trees.

Make.com can automate most of your SaaS lifecycle without custom backend glue code. From trial activation emails to failed-payment recovery and expansion triggers, its scenario builder can connect Stripe, Auth0, your email platform, and your CRM in one flow.

Below are the first scenarios most SaaS teams should implement, including two full blueprint walkthroughs.

Most teams use Slack for communication but still rely on someone manually typing status updates, copying alerts from one tab to another, or pasting reports into channels. Make.com eliminates that entirely — you can connect Slack to any app or data source and send precisely targeted messages without writing a single line of code.

This guide covers everything from basic message sending to building interactive bots that respond to button clicks, watch channels for keywords, and aggregate standup updates into a single daily summary.