So far I have created 25 separate Mastodon API capability collections, allowing me to automate common things I do with accounts, bookmarks, favorites, followers, lookups, post of statuses, searching accounts, hashtags, and statuses, timelines, trends, as well as verify my account. I'll keep building out new ones and augmenting them based upon my needs or what I hear from others. Feel free to fork and use! https://www.postman.com/api-evangelist/workspace/89a20890-1ad3-47d7-850c-51f678e1a716/overview
@ramsey Yes you can! You can run manually using runner, schedule from different cloud regions, and use via CI/CD. I have separate environments for different accounts / instances that I pair with the collections. So I pull content from API, then post with Mastodon API to specific instance.
@kin I’ll have to check that out. Is it pretty easy to figure out how to fork your collections?
@ramsey Should be. Just fork collection and you'll have to add your key -- then the menu for your collection will allow you to schedule as monitor.
@ramsey Let me know if you struggle -- my goal is to make as frictionless for newbies as I can.
@kin Where's the fork button? I'm sure it's right under my nose, but I'm not finding it 🙂
@judell You suffer from same condition as me. Mouseover each collection and each one has a star and three dots.....everything you need is under three dots.
@kin This looks super handy, thanks.
Now I'm looking for where to tell it my baseUrl.
@judell Look under the environments tab. I have an environment for each instance.
@judell So I can abstract away baseUrl and token for each instance I am working with.
@kin Oh I think I see. You fork per-capability, not per-collection?
@judell A collection is just a wrapper. I can make as big or as small as I like -- capability collections are just single use to reduce cognitive load and allow me to share individually.
@kin I haven’t looked at Postman since probably 2018. Can you set up automations in it now? Could I schedule Mastodon posts with it?