So, I spend a long time trying to set up PESOS for individual silos on IFTTT, specifically Facebook and Instagram, because they are terrible. I’ve got it currently set up to publish my initial post, but no back feed support yet. Also, this is going to wordpress, but it shouldn’t matter (in theory, because all software is terrific in theory)

Since I got a headache, I figured that someone else might get one, so let’s save them the pain and I’ll just post the templates for my recipes webmentions. You’ll need to get an auth token for your micropub endpoint. This IFTTT recipe is set up as a webhook, and the trigger will be your silo. The URL should be your micropub endpoint. Replace all instances of ACCESSTOKEN with your generated token value.

Facebook Status Update:


access_token=ACCESSTOKEN&&content=<<<{{Message}}>>>&h=entry&category[]=facebook

{{Message}} is the message of the contents. Facebook is the category. Remove category[]=facebook if you don’t care about that.

Facebook Photo Post:


access_token=ACCESSTOKEN&content=<<<{{Caption}}>>>&photo[]=<<<{{ImageSource}}>>>&h=entry&syndication=<<<{{Link}}>>>&mp-syndicate-to[]=flickr-bridgy&category[]=facebook 

{{Caption}} is the text of the post. {{ImageSource}} is the URL of the picture. Only use the syndication part if you want your site to link back to your post. mp-syndicate-to[] syndicates the photo to flicker via bridgy. Omit if you don’t use bridgy, or you don’t wish to syndicate.
Instagram Photo Post:


access_token=ACCESSTOKEN&&content=<<<{{Caption}}>>>&photo[]=<<<{{SourceUrl}}>>>&h=entry&syndication=<<<{{Url}}>>>&mp-syndicate-to[]=flickr-bridgy


This is almost identical to above.

Obviously, you probably don't want to just cut and paste. You'll want to look up the micropub documentation.
Anyway, I hope that helps. PESOS is not as good as POSSE, but Facebook decided to lock down writing rights after the scandal with reading rights, so what can we do except being bitter?

21 thoughts on “IFTTT Recipes for PESOS

  1. Replied to IFTTT Recipes for PESOS by Charlotte Allen (charlotteallen.info)

    So, I spend a long time trying to set up PESOS for individual silos on IFTTT, specifically Facebook and Instagram, because they are terrible. I’ve got it currently set up to publish my initial post, but no back feed support yet. Also, this is going to wordpress, but it shouldn’t matter (in theor…

    This is some brilliant work. Thanks for puzzling it all out.
    I do have a few questions/clarifications though so as not to be confused since there are a few pieces you’ve left out.
    For the IndieAuth token, which is created at /wp-admin/users.php?page=indieauth_user_token one only needs to give it a title and the “create” scope?
    For the “then” portion that uses IFTTT.com’s Webhooks service are the following correct?
    The URL is (when used with WordPress) of the form: https://example.com/wp-json/micropub/1.0/endpoint
    The Method is: POST
    The Content Type I’m guessing based on the Body field you’ve included is: application/x-www-form-urlencoded
    For your Pocket example, it looks like you’re using the Post Kinds Plugin, so I’m guessing that you could have gotten away without the {{Excerpt}} and {{Title}} portions and just have sent the URL which Post Kinds picks up and parses to give you your context portion with a title and an excerpt anyway?
    It looks like part of the trouble of this PESOS set up is that you’re too reliant in the long run of relying on Pocket (or other services) being around in the long term. If Pocket disappears, then really, so does most of your bookmark, which ideally should point to the canonical URL of the content you’re bookmarking. Of course perhaps IFTTT may not give you that URL in many cases. It looks to me like the URL you’re bookmarking would make a more appropriate syndication link URL.
    For most of my bookmarks, likes, reads, etc. I use a plugin that scrapes my post and saves a copy of the contents of all the URLs on my page to the Internet Archive so that even in the event of a site death, a copy of the content is saved for me for a later date.
    In any case, I do like this method if one can get it working. For some PESOS sources, I’ve used IFTTT before, though typically with RSS feeds if the silo provides them. Even then I’m often saving them directly to WordPress as drafts for later modification if the data that IFTTT is providing is less than ideal. Sometimes worse, using RSS doesn’t allow one to use Post Kinds URL field and parsing functionality the way your webhook method does.

Leave a Reply