# Make and Market Monolith

Availability: Instructions published.
Connection status: Connection not available.

Last reviewed: 2026-08-28.

Plan a Make scenario with explicit credentials, limits and execution identity. A Market Monolith Make connection is not available in this release.

## The client model

Make's [HTTP app documentation](https://apps.make.com/http) describes general-purpose HTTPS requests and dedicated credential handling. A generic HTTP module is not a native Market Monolith app or evidence of a tested scenario.

Use the platform's approved secret-handling mechanism. Do not place a key in a URL, shared scenario field or exported example.

## Design the scenario

Assign a dedicated application and owning account. Review scenario sharing, operation logs and data retention. Define the smallest input set required for the intended outcome.

Set a bounded schedule and explicit stop condition. An iterator or retry branch can multiply requests; it must not turn one approval into recurring paid authority.

## Future asynchronous work

Save the accepted operation identity and retrieve its result. A callback, successful module run or partial output is not proof of final completion, fulfillment or settlement.

Do not automatically rerun an uncertain paid operation. Follow [Operations and results](/docs/operations-results) and the future operation-specific contract.

## Availability and support

Instructions are published; connection is not available. Make owns its HTTP module, scheduling and execution history. Market Monolith owns any future published API contract. No native module or working connection has been verified.