1 2 3 ... 8

A shorter update this week. First of all, congrats to Slack on launching their brand new Workflow Builder! As many of you know, Slack was one of our earliest investors, in 2017. We've been working closely with them ever since — and unlocking new ways for developers and makers to build Slack apps has always been a shared passion. Congratulations especially to Mike Brevoort, founder of Missions which was acquired last year to help Slack ship a great addition to their product.

In celebration, we've launched our own Slack Welcome Page where Slack app builders of all sorts can connect Slack to any API ecosystem available on Standard Library. As time goes by, the delineation between "no code", "low code" and even professional developers will continue to blur. We're excited to play a small role in building what's to come, stay tuned for more updates on our end and keep an eye on Slack's platform!

A preview of our new Slack welcome page is below:

Build Slack Apps

A Social Change

In addition to celebrating the growth of Slack's platform, we'd also like to announce we've changed our Twitter handle from the old "StdLibHQ" to @StandardLibrary. This is an ongoing part of an iterative rebrand and reimagining of the company. The types of folks we're helping deliver outcomes for now are looking different, in many ways, than the ones we started with. The company name is important to us, as is our domain (stdlib.com), but approaching the broader community with a more professional vibe is something we're looking forward to. Feel free to Tweet at us!

As usual, if you're looking for help — or just people to hang out with — click here for an invitation to our developer Slack channel.

Keith Horwood
Founder and CEO, Standard Library

Hey all! Hope all is well. This week we're coming in live from New York City at ServerlessConf 2019 with some major polish updates to your Standard Library experience.

We've completely redesigned the homepage to better reflect our tooling and product suite. You can now opt to create workflows directly from our main page, stdlib.com. We'll automatically generate code for you, which you can see on the right (on desktop). Here's the codegen in action.

A new look

The team wants to note that we've always provided this functionality! It was unclear to many new users since our launch of Product Hunt → Build on Standard Library that codegen / hosting was something we were offering behind the scenes. The goal of the website redesign was to just be clearer about how our products work together: there's a lot!

New Logo

Along with the redesign, we've upgraded our logo a little bit. We added a third dimension! As we mature as a company and product suite, we felt it was important to convey the "building block" nature of API development we offer. We've got T-Shirts with the new logo that will be available starting today at ServerlessConf, but if you see us at meetups or conferences feel free to ask for one.

We want to thank Scott Gamble (@threesided) for his work here. He's been responsible for most of our logo work since day one and a number of past iterations of our website design. You can check out his studio at Threesided Creative — highly recommended!

Deploy Pre-Built Projects from GitHub

Additionally, we've added in a section that allows anybody to get started building Standard Library workflows from pre-built projects on GitHub. This functionality has existed for a while, but we weren't showing it off! Simply visit stdlib.com and scroll down to the Ready to Get Started? section. You can star the repositories on GitHub or simply opt to deploy them right away.

Get Started

That's it this Week

We're excited be able continue to iterate on our product and development experience. Thanks for staying tuned. Follow us on Twitter, @StandardLibrary, or click here for an invitation to our developer Slack channel.

Looking forward to seeing what you make!

Keith Horwood
Founder and CEO, Standard Library

Hope you're all doing well! It's been an eventful couple of weeks at Standard Library, and I've got two exciting Build on Standard Library updates to share:

  • An overhaul of our Linked Resource management pages
  • Support for Slack block actions

Let's dive in!

Easier Linked Resource Management

The new Linked Resource page organizes your resources by API provider, making it easier to see at a glance which API ecosystems you currently have linked to your Build on Standard Library workflows. You can also link new resources here if you wish to do so outside of the workflow creation flow, which can be useful if, for example, you've shipped a workflow triggered via slash command in one Slack workspace, but you've realized you want to use it in a different workspace instead.

Provider

If you select a provider from the list, you can see all of the resources you've linked for that provider neatly grouped by account — in the example below, all of the resources are part of the Testbit Slack workspace.

Linked Account

Clicking individual resources will bring you to a management page where you can see which Identities you've linked the resource to. You can also delete the resource if necessary under the Advanced tab.

Linked Resource

Additionally, clicking the header for a group of Linked Resources will bring you to a new page summarizing their shared external account. From that screen, you can delete the entire account and all of the associated resources at the same time.

Slack Block Actions Support

We now support Slack block actions as events in Build! Slack blocks allow more in-depth formatting options over Slack attachments, and enable you to create complex, customizable workflows within Slack. You can get started by going to build.stdlib.com, selecting Slack as the event source, then the block_actions event and a block_id identifying which blocks your workflow should respond to.

Block Setup

After you set up a workflow, you'll need to generate a message containing blocks, which you can do using the Slack channels.messages API.

Block Action

In the above example, we have a workflow that responds to a block with block id food-choices, which contains buttons. Here's the syntax that generated that block — note the block_id parameter value:

  {
    "type": "actions",
    "block_id": "food-choices",
    "elements": [
      {
        "type": "button",
        "text": {
          "type": "plain_text",
          "text": "Farmhouse",
          "emoji": true
        },
        "value": "Farmhouse"
      },
      {
        "type": "button",
        "text": {
          "type": "plain_text",
          "text": "Kin Khao",
          "emoji": true
        },
        "value": "Kin Khao"
      },
      {
        "type": "button",
        "text": {
          "type": "plain_text",
          "text": "Ler Ros",
          "emoji": true
        },
        "value": "Ler Ros"
      }
    ]
  }

For more information on Slack blocks and their syntax, check out Slack's documentation.

Thank You!

Thanks for reading! If you'd like to keep up with the latest news around Build on Standard Library, follow us on Twitter, @StandardLibrary, or click here for an invitation to our developer Slack channel.

We can't wait to see what you build!

Jacob Lee
Co-Founder, Standard Library

I'm pleased to bring you all two very exciting pieces of news this week: we've published an official Standard Library Slack app that provides a faster, more streamlined way to integrate Slack into your Build on Standard Library workflows, and we've added a new member to our team, Kevin Brimmerman!

A Faster Way to Build Slack Apps

Over the past few years, thousands of developers have created Slack apps on Standard Library. It's always been a great use case for the platform, but the process of setting up a project involved multiple trips to the Slack app dashboard to retrieve app secrets, paste webhook URLs, set up authentication, and more.

We've now simplified linking Slack to an Identity in Build on Standard Library to a four click process — first, select the new "Standard Library App" flow from the dialog:

First Step

Next, install the Standard Library Slack app into your Slack workspace using the OAuth popup:

![Second Step](https://stdlib-dotcom.s3.amazonaws.com/static/blog/introducing-a-faster-way-to-build-with-slack/ScreenShot2019-09-18at9.02.15 AM.png)

And finally, add some optional customization:

Third Step

As before, you have the flexibility of calling any of the Slack APIs on Standard Library with your linked Identity Token, and you can seamlessly run any code-based workflow that integrates any other API provider (Airtable, Twilio, Stripe, etc.) in response to events in your Slack workspace. You can even associate separate nicknames and icons with different workflows to provide distinct experiences within a single workspace!

Workspace

We've retained the old method of creating Slack apps because it provides some specialized capabilities that the new flow does not, such as the ability to add external data sources to dialogs, dropdown menu items to messages, and to set up distribution on the Slack app store. We've renamed apps created through that method "Custom Internal Apps". If you need complete, fine-grained control over your integration, the tried and true model is still there for you.

Welcome, Kevin!

We're thrilled to add Kevin Brimmerman to the Standard Library engineering team! Despite being a Cubs fan, he brings infectious energy and a wide array of talents to the team. Pop into our developer Slack channel and say hi, and if you haven't checked out his article on setting up a status page on Standard Library, you definitely should. It's great stuff!

Thanks for Reading!

If you have any questions or comments, please join our Slack workspace to talk to us as well as the community at large. You can also follow us on Twitter, @StandardLibrary.

Jacob Lee
Co-Founder, Standard Library

Hey everyone! As the summer winds down, we wanted to make sure we launched a very important feature of the platform. Since we first announced Build on Standard Library people have been asking, "how do I create my own Connector APIs?" We're pleased to announce that the process of building your own reusable APIs for use in setting up workflows is now a straightforward process. You can Build Your Own Connector APIs easily, and we even have a template to start.

Build Your Own Connector APIs

To build your own Connector API, we've provided a very easy template that you can deploy from GitHub using our Deploy from GitHub button. It's available on GitHub: stdlib-examples/connector-pokefusion.

The example is a Connector API that provides Pokemon Fusion capabilities, and can be used in any app you build. For example, our team has built a /pokefusion Slack slash command.

Pokefusion Dropdown

Pokefusion Result

To get started and implement your own Pokefusion API, head over to GitHub: stdlib-examples/connector-pokefusion. Follow the README and deploy directly from the example! You'll need to make sure you publish a version of the API before you see it available in the dropdown.

Changing an API to a Connector API

Additionally, any API you build on Standard Library can be changed between a Workflow API and Connector API from the project page. In order to appear in the Build on Standard Library UI, an API must both be classified as a Connector API and a version (release) must be published.

Simply click the lock icon to the right of the Connector API dropdown, and voila!

Select the project type and you're all done! Please note that Connector APIs can not respond to events.

Happy Building!

That's all this week, if you'd like help please feel free to join our Slack workspace for help from us and the community. You can also follow us on Twitter, @StandardLibrary.

More coming soon!

Keith Horwood
Founder and CEO, Standard Library
1 2 3 ... 8