:markdown
  # Webhooks

  Webhooks allow you to run custom code when one of your scrapers has finished
  running on morph.io. When a webhook is triggered, we'll send a HTTP POST
  request to the webhook's configured URL. Webhooks can be used to transform
  data into different formats, send out notifications, update an archive, or
  even run some realtime analysis.

  Webhooks can be installed on any of your scrapers. Once installed, they will
  be triggered each time that scraper finishes running.

  ## Payloads

  Webhooks currently just make an empty HTTP POST request to the specified url.
  If you'd like the webhooks to have some state you'll need to put that state in
  the webhook url, either as the path or as GET parameters. If there's something
  specific you'd like included in the webhook payload then please
  [ask a question on our help forum](https://help.morph.io/).



:markdown
  # Webhooks

  You can use webhooks to trigger actions in external services
  every time one of your scrapers finish a run.
  You can use this to do all kind of things:
  send emails when a scraper is finished;
  immediately pull fresh data from a scraper’s API;
  or run realtime analysis—anything you like really.

  Add *webhook URLs* under the **Webhooks heading
  on your scraper’s Settings page**.
  Every time your scraper finishes a run
  we’ll make an HTTP POST request to each URL you’ve added.
  Use this request to trigger your custom code.

  ## Payloads

  Webhooks currently just make an empty HTTP POST request to the specified url.
  If you'd like the webhooks to have some state you'll need to put that state in
  the webhook url, either as the path or as GET parameters. If there's something
  specific you'd like included in the webhook payload then please
  [ask a question on our help forum](https://help.morph.io/).



Make the description and webhooks and their benefits clearer
Make the description and webhooks and their benefits clearer

Currently the webhooks description is unclear, particularly for new
users to morph and people who are new to webhooks.

See: https://github.com/openaustralia/morph/issues/957

This reworks the text to:

* be home user centered;
* focus on and be more specific about the benefits to the user
* provide more concrete examples
* actually direct people to where they can add webhook urls
* provide a clearer explanation of what webhooks are
