// Submit a module

List your module in two minutes.

Paste the npm name. Your browser checks the published files (src/modules and dist/modules), the license and the date a fresh app can install it, then builds the descriptor with the same schema as CI. You open the pull request; a person merges it.

modules/@northbound-run/channel-cloudflare-email.ymla listed entry, the whole file

npm: "@northbound-run/channel-cloudflare-email"
github: Northbound-Run/open-mercato-cloudflare-email
category: communication
tags: [email, cloudflare]
summary: "Cloudflare Email Service channel: inbound mail through Email Routing and a Worker, outbound through the REST API."
whenToUse: Use when your domain mail runs on Cloudflare and threads should land in the app's communication channels with real delivery status.
whenNotToUse: "There is no history import: the channel sees mail only from the moment its routing rule goes live."
providers:
  - { name: cloudflare-email, label: Cloudflare Email Service }

The checks run in your browser and need JavaScript. Without it, add modules/<scope>/<name>.yml in a pull request (the file above is a full example) or request a listing.

// Preview

Paste a package name and press Check. The preview shows the row and the file your pull request adds.

Building a module?

Publish it with create-mercato-module, then paste its npm name here.

What happens next

CI checks the file and writes a short summary in the validate check of the pull request. After merge the module is read from source within minutes and installed in the next run of each line.

Rules

English, plain text, no links in the summary. Screenshots are optional. Measured fields are never in the file. See the contributing guide.