Jump to content


  • Content Count

  • Joined

  • Last visited

About johnthepink

  • Rank

Recent Profile Visitors

356 profile views
  1. Just published 2.1.5 which should fix errors relating to the folder names.
  2. I just published version 2.1.2, which now supports returning more than 15 projects. I also confirmed it is working fine with Alfred 4. However, you may need to update a folder name depending on what is currently installed on your system. See this issue for the fix: https://github.com/johnthepink/alfred2-basecamp/issues/10
  3. @mhanes @jlogan you are right, I have not tested this with Alfred 4. I will try to get some time soon to address.
  4. Thanks for writing up a handy Alfred workflow!

  5. Thanks. What does the actual log say? In /Users/antonio/Library/Logs/Alfred-Workflow.log
  6. antonio, I have recently updated the workflow to support Basecamp 3, which requires you to obtain a token to authorize your account. I posted the steps earlier in this thread, but you can also follow here https://github.com/johnthepink/alfred2-basecamp If that doesn't help, could you please post the error message alfred gives you?
  7. Just added a new build with a quick fix for token expiration. I'm trying to think of a better way to handle this in the future.
  8. Basecamp 3 Support! Hey everyone. I've added support for Basecamp 3 to the workflow (Basecamp 2 support still works). Whether you are using Basecamp 3, or Basecamp 2, if you update there is now a different process for authenticating. Visit this site to retrieve your Basecamp token Right click on the “bc” Script Filter and click “Configure”. Fill out your Basecamp information. Note that if you belong to more than one organization, you can enter them separated by commas. Organization ids can be found in the Basecamp URL: https://basecamp.com/xxxxxxx. The x’s are the ID you want. Each
  9. Do you mind pasting what you have as the settings with your password xxxxxx-ed out?
  10. Davduf, Are you still getting the same error? #<URI::InvalidURIError: bad URI(is not URI?): https://basecamp.com/[dufresne@davduf.net]/api/v1/projects.json> That makes me think it's a problem with your settings. Your email with brackets shouldn't end up in the URL. That should actually be a basecamp company id. Do you mind pasting what you have as the settings with your password xxxxxx-ed out?
  11. Hey Davduf, Could you double check your settings by right clicking on the "bc" script and clicking "Configure"? basecamp_username="putusernamehere" basecamp_password="putpasswordhere" basecamp_email="putemailhere" basecamp_company_ids="basecamp,ids,separated,by,commas,here" It looks like you may be using the brackets, either remove those, or wrap your credentials in quotes like above.
  12. Hey all. I have got Basecamp 3 support working, and I will be shipping it shortly. They are about to make a breaking change that I am waiting on before I hand it over to you guys. See here if you're interested: https://github.com/basecamp/bc3-api/issues/2 Thanks!
  13. Just an update. Basecamp have begun to open up their Basecamp 3 API. I have gotten early access, and am chatting with them about the best way to proceed. Hopefully I will have some more information soon. Thanks!
  14. Hey Austin, I just looked in to adding Basecamp 3 support, and it looks like Basecamp hasn't released their API for v3 yet. They mention here that they plan on offering an API, but there is currently no timeline for it. I'm tracking the issue, so as soon as they announce it I will update the workflow. Sorry about the wait. Thanks!
  15. Austin, Glad you're getting some use out of it . I will try to take a look soon concerning Basecamp 3 support. Thanks for the heads up!
  • Create New...