Connect Combell Public and Readme Endpoints
Describe what you want to happen between Combell Public and Readme Endpoints in plain words. HumDay writes the program, proves it on real data, and runs it — no node graph, no field mapping, and no connector to wait for.
What HumDay can do on each side
Read from each provider’s own published API description, in their words.
Combell Public
75 documented operations. See all Combell Public operations
- POSTCreate a new mysql user
/mysqldatabases/{databaseName}/users - POSTCreate a new account
/accounts - POSTCreate a new mailbox
/mailboxes - POSTCreate a new mysql database
/mysqldatabases - POSTCreate a record
/dns/{domainName}/records - POSTCreate a new alias
/mailzones/{domainName}/aliases
Readme Endpoints
28 documented operations. See all Readme Endpoints operations
- POSTCreate custom page
/custompages - POSTCreate version
/version - POSTCreate changelog
/changelogs - POSTUpload an API specification to ReadMe
/api-specification - DELETEDelete custom page
/custompages/{slug} - PUTUpdate custom page
/custompages/{slug}
How a Combell Public and Readme Endpoints automation gets built
- Describe the outcome. Say what should happen — not which endpoints to call. HumDay works out which operations each side needs.
- Approve the contract. Before anything is built you see exactly what it will do in Combell Public and Readme Endpoints, and what it will never do.
- See it proven. The program runs and shows you the result before it is allowed near either live account.
- Grant access, then go live. You approve the specific operations it may use on each side — and only those.
Related integrations
- Combell Public and OData for namespace microsoft.graphintegration
- OData for namespace microsoft.graph and Readme Endpointsintegration
- Cloudflare and Combell Publicintegration
- Cloudflare and Readme Endpointsintegration
- Combell Public and NetBoxintegration
- NetBox and Readme Endpointsintegration
- Combell Public and GitHubintegration
- GitHub and Readme Endpointsintegration
- Combell Public and Mistintegration
- Mist and Readme Endpointsintegration
Questions about connecting Combell Public and Readme Endpoints
- Can Combell Public connect with Readme Endpoints?
- Yes. HumDay reads both providers' own published API descriptions and derives what each one can do, so neither side needs a hand-built connector before you can use it.
- How do I connect Combell Public to Readme Endpoints?
- Describe the outcome you want in plain words. HumDay agrees a contract with you saying exactly what it will do, writes the program, and shows you a proof run before either account is touched.
- Do I need to write code to integrate Combell Public and Readme Endpoints?
- No. There is no node graph to wire up and no field mapping to do. You say what should happen and HumDay works out which operations it needs from each side.
- What can HumDay do across Combell Public and Readme Endpoints?
- Combell Public publishes 75 documented operations and Readme Endpoints publishes 28. HumDay only ever uses the specific ones your approved contract needs.
- Is it safe to connect both accounts?
- Your credentials are stored encrypted and never appear in chat, code, or logs. Anything that writes to either Combell Public or Readme Endpoints is held behind an approval you grant explicitly.
Where this came from
Operations are read from the published API descriptions for Combell Public and Readme Endpoints. Descriptions are each provider’s own words, not ours.