I\u2019ve used a variety of approaches over the years, from manual to semi-automatic. Here\u2019s some different things I\u2019ve done:
\n\nInitially I would publish a note, then use the interactive Bridgy Publish form from my account page. Your account page is https://brid.gy/twitter/isellsoap. Paste the URL of your note there, choose the options whether you want your original link appended to the tweet, then preview it. If it looks good, publish it. I then would copy the tweet\u2019s URL and add it on my original note as a syndication link. See below on this note for an example of that syndication link.
\n\nAfter I did that for a while and it was working smoothly, I started to automate it more. Bridgy Publish lets you send a webmention to trigger the publish. I set up a custom bit of PHP code that would let me click a button to send off that webmention for the note I wanted to publish. Sending a webmention is a pretty simple POST request, so I used the WireHTTP class for that. When publishing to Twitter, the successful Bridgy response includes the Twitter API data for the tweet. I wrote some more code that processes that response to get the tweet\u2019s URL and updates the syndication link on the note.
\n\nNote that all of this is separate from the Webmention plugin itself. The code for my semi-automatic publishing isn\u2019t part of a plugin and isn\u2019t very polished code, so I haven\u2019t released any of it. If I can find a way to make it more user-friendly, I might release it, or at least write a tutorial with more guidance.
\n\nhttps://php.microformats.io is a useful tool to debug the microformats in your posts, by the way. Here\u2019s the parsed result of this very note. The in-reply-to property is what Bridgy Publish uses to post a reply tweet. The syndication property is one way Bridgy maps your original post to the Twitter copy for sending responses back to you \u2014 particularly if you don\u2019t include your original post link in the tweet.