Maybe a workaround for the markdown would be to add an option to not send the post content itself... only user, discussion title, etc.

Otherwise, I wonder how the flarum email notifications work. They get sent as HTML but without any formatting, maybe the same method could be leveraged for getting unformatted post content.

14 days later

0.5.0

  • NEW: Allow using Slack adapter with any URL for Slack-supported webhook endpoints on any service
  • NEW: Add option for transforming post content into plain (unformatted) text
  • NEW: Add option for limiting post content payload to a certain # of characters
  • Backend refactor of Actions to allow for some features mentioned above
    • If you or an extension adds actions/events to fof/webhooks, there are breaking changes
      • ignore method signature has changed

Updating

composer require fof/webhooks
php flarum cache:clear
10 days later

This webhook is disabled because it doesn't have any events enabled, What does it mean and how can I solve it?

    CosmicLivest Once you create a webhook, you need to click the edit button to enable the events you want to receive hooks for.

    a month later

    does this work for discord posting when someone posts threads etc

      Puggo That is correct. You can set it up so when someone creates a discussion it'll post about it on a Discord channel.

        Puggo What doesn't work? What have you tried? You need to create a hook on Discord, copy its URL & put it into the extension's settings, and enable the Discussion Started event.

        not working for me, do you think i did something wrong?

        Puggo Sorry, I hadn't seen this message. You'll want to recreate the webhook as anyone with that URL from the screenshot will be able to send messages in that channel.

        Based on the screenshot, you didn't click the + icon to actually add the URL & service. Once you do that, you'll want to click the ✏️ button to edit it, and enable the events you want, e.g. "Discussion Started"

          if i could upload files i would, but i cannot.

          Puggo Try updating to 0.5.1. I don't think it'll fix the issue you're having of "url is required", but it should fix the extension completely breaking the admin panel (at least for the case I could reproduce locally).