Create a new heartbeat in elmah.io

What this operation does

Create a new heartbeat.

• POSTChanges data · Heartbeats/v3/heartbeats/{logId}/{id}

How HumDay uses it

1. You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
2. The contract names it. Before anything is built, you see exactly which elmah.io operations the program may use, and this is one of them.
3. You approve access. Because this one changes data, it cannot run until you have explicitly granted it.

Other elmah.io operations

• Create a new messagePOST · changes data
• Deletes a list of messages by logid and queryDELETE · changes data
• Create a new logPOST · changes data
• Create a new deploymentPOST · changes data
• Mark a list of messages as fixed by logid and queryPOST · changes data
• Create one or more new messagesPOST · changes data
• Create or update a translation between a minified JavaScript pathPOST · changes data
• Delete a message by its IDDELETE · changes data

All 22 elmah.io operations

Questions

Can HumDay create a new heartbeat in elmah.io?

Yes. This operation is published in elmah.io's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.

Will this change my elmah.io data?

Yes — this is a POST operation, so it changes something in elmah.io. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.

Do I need to write code?

No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your elmah.io account.

Where this came from

Read from a published API description for elmah.io at api.elmah.io/swagger/docs/v3. The description above is the provider’s own wording, not ours. Last published 2023-03-06.