Transcript for "Learn Gamma's API - No code required": Alright. Good morning, everybody, or afternoon, evening, depending wherever you are. I'm Max. I lead API support here at Gamma. Before we get started, just a couple of housekeeping notes. The recording is gonna go out after the session today, so there's no need to take notes. We have a lot of great content to cover, so we're not gonna be able to do a live q and a. But my colleague, Dejo, and a community member, Chowder Miller, will be keeping an eye on the chat to help answer your questions. So you're in good hands. Also, if you're calling in from our ambassador community or you've built with our API before, feel free to jump in and help out. We only learn through each other. I also won't be, watching the chat myself, but we're gonna have a lot of great information to share with a follow-up email after the session today. So but also one other thing about Zoom, I'll do my best to kinda zoom into Windows to show you all the stuff I'm working on. But, in case it's not big enough for you on your view, Goldcast, the platform we're using, allows you to zoom in. Okay. So just on a high level today, what we're gonna be building is, you know, meeting notes go in and a branded deck comes out fully automated. Granola captures the call, and Zapier connects everything, and Gamma does the heavy lifting. No code. Click through setup, and you'll get to see exactly how it works. Alright. One second here. Give me one second here. Alright. Thanks for bearing with me here. So today's agenda, we're gonna kinda go over all these points listed above. But on a high level, it's gonna be kind of the how the the how and why, and then we're gonna connect all these pieces together. So as I mentioned before on the previous slide, Dejo, my colleague, and Chowder Miller will be answering questions in the chat if you just came into the session. But before we get started on building, you know, a lot of workshops kinda just go straight into it. I wanna kinda give you more context for, you know, what is an API, when and why you'd wanna automate, and what our API can do, and then how we can connect all those pieces together. So let's start with talking about when you should automate because you don't necessarily need to every time. I I find that the five x rule is a really great place to start. Five x meaning if you're doing something, you know, five times a day, five times a week that, is kind of repetitive copy and paste sort of work, you know, in the context of Gamma. You know, if you're you have a deck you really like and you're just saving it again and replacing all the information, even working with our agent or, you know, in any context, if you feel like the creative work itself isn't really being done, but the, you know, route kind of formatting, copying is is happening, you know, on, you know, a daily basis and it's kind of slowing down your workflow, it may be something worth automating. This is especially true if you're autumn if you're doing a certain task even more than 10 times a week or a day, it'll you know, and it has that same structure. At that point, if you're, you know, a business owner or whatever kind of professional, you're probably losing money just wasting that time. But there's also times when you shouldn't be automating. You know, there are many complex workflows in the community, but sometimes you need to, you know, push things pixel by pixel. Sometimes you're making a bespoke deck that is really just for a keynote or a specific client, and you really need that extra touch. In those cases, automation really probably isn't the best fit for you. And because in that case, unique is the selling point. So before you decide when to automate, you should ask yourself, like, could I hand this in to someone and just have them do it based on a list? Am I just copying and pasting? You know? Then that's probably a great workflow to automate. But, you know, since we're here to learn about automation, you know, and everyone on this call, you know, has a pro account or above on Gamma, It's a feature you already have. Worst case, you know, you waste an hour of your time. Best case, you save a lot of time. And so it's definitely, you know, worth considering, which I imagine why many of you are on the call today. So what is an API? An API stands for application programming interface, which for those of you who aren't technical, might just kinda sound like a lot of tech gobbledygook. But let's walk with me for just doing, like, a little bit of an analogy. So when you go into a restaurant, you don't walk to the back and start cooking your own meal. You sit down and you order your meal from a waiter who goes back to the kitchen and brings you your food. So in this analogy, the the menu you're ordering from is our API documentation. The server is the API request, and the kitchen is Gamma's back end. So on you know, to continue this, you know, when you place your order, you're basically sending a request to what we call on our API post endpoints, which means that you're sending in information and hoping to receive something back. Gamma's API is what's called asynchronous, where you you wait a little bit for the for the food to be ready or your deck in this case, And so we have what's called a get status endpoint that will give you the status of your deck and when it's finished being created. But to boil it boil it all down, basically, you're, you know, you're placing orders with code via number of different tools instead of clicking buttons in the Gamma UI you know and love. To kinda continue the analogy, you know, when you go to restaurant and order food, you know, you may want your burger cooked a certain way. You may want to remove chicken from your salad. Whatever it is, you know, you want some level of customization, and that correlates to what we call an API's parameters or options, basically. So with Gamma's API from the create from template endpoint that we're gonna walk through today, that'll be something like which template you choose to use, what content you wanna fill in, the theme to apply, things like that. So but another takeaway for this is just the parameters are the settings you already know in Gamma. So they're you're basically just preselecting those options and letting it happen. Okay. So what can Gamma's API do? So Gamma's API can do you know, generate presentations from text either from, like, super custom from our generate endpoint, which allows you to change everything from, you know, the header, footer, custom images, and, you know, we're we're adding more functionality all the time. So that's, like, the slash generate endpoint. What we're gonna be working with today is the create from template endpoint, which is correlates to our remix feature, which just came out of beta. So but, yeah, you know, this API kinda allows you to brand every deck consistently, add your logo, and instead of doing it by hand, it can be processed in a couple of minutes. So the tool we're gonna use today to automate this process is called Zapier. Zapier is a visual inter interface that allows you to interact with APIs. So and it's simple as, you know, a trigger and an action. So, basically, if something happens, create a deck. Zapier is a great tool, but definitely isn't the only tool for this. Many people in our community really enjoy working with, make.com or n a n, Workato. There's a million of different integrations you can use for your use case that best fit. Zapier is a great and popular one with a lot of connections, so we're gonna go through that today. So now that I've given you kind of all the the tools, the understanding of what an API is, when to automate, what our API does. Let's think about a a use case. So Meet Positive Progress, they're a dog training business that consults with clients to help their dogs behave better, have a better time in their families. So, you know, the pattern, though, is very, familiar to anybody who has the similar workflow. You know, you consult with a client and provide your expertise and knowledge, you know, whether you're working in sales, you're an entrepreneur, you know, any you know, I imagine all of you have a reason to join this call today so you can think about what makes the most sense for you. And that high value work is really, you know, where you get to spend your time. Now what we call the low value work is, you know, once you finish that call, you know, you wanna have a deck to present details about your call, what your next steps are gonna be, and that's kind of the the tedious work that we're trying to automate today. So same structure every time, but different details. So now if we kinda continue with this, you know, if you're, you know, spending, you know, twenty to thirty minutes on every deck trying to reformat it for your client, trying to make it reflect all their details, play with the layouts, you know, work with our great agent system. You know, still, you're spending about thirty minutes at a time. And, you know, over the course of a week, that can be, you know, five to seven hours of just formatting, which can almost equate to a full days of work. And, you know, when you're getting to that point, you're having good problems, basically. You know, if you have enough business, you have enough consultations, you know, your process is almost disincentivizing you to grow because you're spending so much time doing the same thing over and over again. So instead of this thirty minute process, what if it could happen in a few minutes? So what we're gonna the other tool we're gonna work with today is called Granolah. Granolah is a great AI notetaker app, that captures Zoom or Google Meet calls, really kinda any call automatically, and then takes the content of your transcription and makes it into a formatted list of notes, which is perfect for automation use cases. They've been kind enough to also offer a code for those who are participating in the workshop today, which is on the screen here. We'll also send that code in our follow-up email so you can get started with Granolah if it sounds like it works for you. But, you know, if you've never heard of Granolah or it's not a tool you're familiar with, you know, this this is just one tool you could probably you can connect. Every workflow is different, and I want you to take away today, you know, and start brainstorming what workflows you'd like to do. But I'm just using this because it's a great example. So today, in Zapier, we're gonna build this workflow. It's gonna have a trigger, which is, you know, waiting for an action to take place. So in our case, it's gonna be a note saved to a folder. We're gonna then generate a deck based off of the content of those notes and then wait a little bit for it to process and get that finished deck URL. So four steps. Let's build it. Alright. So let me go ahead and share my whole screen here. Give me one moment. Alright. Thanks for bearing with me here. So right now, positive progress. The business we were talking about has this beautiful deck they made for their client, Bella. It's got these great, very Gamma esque images of dogs and this wonderful texture background talking about a French bulldog named Bella. And so, you know, they spent a lot of time building this deck, and so they decided to make this deck into a template that they can work from. So if I go into positive progress's workspace here, you can see this template view. So now instead of having to, you know, adjust this text manually, they would like all of their clients to have this deck because it represents their brand, and it speeds up the process. So what we're gonna do now is I'll show you a little bit of granola. So granola so this is granola, and this is a meeting notes from about Cooper, a six month year old Australian shepherd puppy. So it's a different details from this note than, of course, in the deck currently. So what if we could just automatically take these details and create a deck right after their meeting? Now let me go ahead and so this is Zapier. As I was mentioning before, this is gonna be our workflow. We're in what's called a test view. And right off the bat, I'm going to show you it running first, and then we're gonna build it from scratch together. So let me zoom in a little bit in case it's hard to see, but let me select test run here. I'll just kinda walk through what's going on. So right now, it's finding the note in granola, creating that temple creating that gamma from the template, and then we're doing that delay step. So while we're waiting for the delay to finish, you know, working in API support, a common thing I noticed with people starting with the API is not allowing for polling or async generation, but to put it in less technical terms, just giving Gamma's back end time to produce your deck. So, you know, whether you're using Zapier or any other tool, I would say having about ninety seconds is a great place to start, so it allows Gamma to kind of finish processing. If I didn't have this delay step right here, it would def it would immediately go to the get generation status, which tells you if it's finished yet and gives you a URL, but it enabled but it would probably just show you pending, meaning it's not finished yet. So we kinda give it some time and build that into our automation since, of course, if we're automating this, we don't wanna babysit it and let it just kind of run the same way every time. This can really vary as well. You know, we have access on Gamma, you have access to some really incredible image models like the famous nano banana. However, Nano Banana is great, but it can take a lot longer to produce high quality images. So I'd recommend, you know, iterating and adjusting your workflow kinda based on on what's of what kind of stuff you're working with. So it looks like the generation status is done. So in Zapier, we can look at the run details here and see that we have this URL. So let me go back to the other workspace here. And now it's about Cooper. So look. Magic. So now all the details, you know, from that granola transcript are in the deck. Presto, change o. Alright. So let's go ahead and build this together from scratch just so you can see how I do this. So as I was saying before, every automation has a trigger and an action. So the trigger, in our case, is gonna be via the granola app. So I'm gonna select granola. I will call out, though, that if you look into Zapier's ad dialogue here, you know, they have over 7,000 apps. There's lots of different tools you can connect. So depending on the use case and the workflow, I mean, you have infinite options, basically. So I'm gonna go over here. I'm gonna choose the trigger event. The trigger event is just what event starts the automation. So in our case, we're gonna do note added to granola folder. So I have a folder defined in granola that the automation is going to look into to see if it had a new note added. I'm gonna go ahead and select my account, and then I'm gonna configure. So select the Gamma workspace here. I'm gonna just call it Gamma API workshop, and then I'm gonna choose that folder. So now but when you're building an automation in Zapier, you have to test every step individually just to make sure it works before you can do a full run through. So we're gonna test here select test trigger. Now if I click on this note, I can see that it's a consultation for Cooper. So many different applications are gonna have a lot of different fields you can pick from, and it's just gonna vary between application to application. We're going back to our, you know, parameters, menu options analogy. You know, these are all options that were selected. So I'm gonna continue with this selected record, and then I'm gonna select Gamma here. So within Gamma, we know we have a native integration on Zapier as well as make and soon to be n a n, and we're going to select create from template, which is actually out of beta, and then we're gonna select the account. So if you're if I was setting this up from scratch, I would have to pull my API key from my account and and then put it into Zapier, but I'm gonna show you real fast what that looks like. I also will call out that you need to treat API keys like passwords. It's just as sensitive. But yell at me. Because if someone gets a hold of your API key, they can basically impersonate you or, you know, use all your credits, which you definitely don't want. But for the purposes of one second here. So if I go into my Gamma workspace and select settings and then API keys, I can create a new API key. So let's call it test. So this is the API key. It's a series of characters. I'm gonna delete this right after. And I will also call out that once you have this API key, you'll wanna store it somewhere secure either in the application or, I mean, as for secure note. But, you know, as as we call out right here, close and hide forever means you'll never see the full API key again, and this is true for many different platforms. So I'm just gonna go ahead and delete that, but I thought that would be useful to show. Me navigate all my windows here. Okay. So one thing also I'm going to talk about is that from this view, you could even if you just did this workflow once it's complete, you'd be able to see a completed API Gamma just in your workspace. You wouldn't even actually have to need to do the other steps that we're doing if that was your main aim. But let me just finish building this. Alright. So for the template Gamma ID, this is something that we need to grab from Gamma. When you create a template in Gamma, each template has its own unique ID that can be used in automation. So if we go back to the client consultation deck and select API and copy it, I can then go over here, paste it in, and now I now it knows to create from that template of originally Bella the dog. Now we so for each of these ones, the only two that are required designated by that red star are is prompt and template ID. So I'm gonna select this. Select meeting my notes, and now it knows to pull from the field that has the bulk of the notes itself. Alright. Now we're gonna test that step. Okay. So next, we're gonna do the flow control or utility step, flow control, and do delay. So like I was talking about before, Gamma's API is asynchronous, meaning that it takes a little bit of time to fully generate, but still comparatively a lot less time than doing it by hand. So I'm going to select the number the unit I wanna use to delay for and then a value. So ninety seconds is about one point five minutes. And then I'm gonna test this step, which is, you know, testing that it's waiting. So the last step is going to be gamma get generation status, and then so this generation ID is a number that's passed from the create from template endpoint. So every time you create it, it basically just gives you an ID to sort of track your order, and I'm gonna go into this step and pull the generation ID and then test that. Cool. So once again, I'm gonna go back here just to show you where it is, but I am looking at the clock. So let me kinda keep this going. But yeah. So all of your API generated decks are gonna show in this API generated section of your workspace. Great. And, really, that's it. We can run this again, but we already saw it in action. But I hope that was helpful. Let me go ahead and get back to the deck, and we can get towards the end of our session today. So, yeah, what I showed you today is just one of many things you can automate. You know, here's a couple of other sample use cases that you can think about. You know, something like using HubSpot meeting notes to save to a Gamma follow-up deck. You know, salespeople really, you know, love our product because you can kinda take all those notes from AI notetakers and create a polished deck about next steps, but also a Google form to onboarding deck if you're emailing a new customer or, you know, maybe internal uses in HR. But, really, the sky is the limit. You know, one thing we're going to share after our session today is some of our kind of champion automations. Like, people in the community have made some really incredible and complex different workflows that can allow you to, you know, have a game and deck process from, you know, everything from CRM stuff like Salesforce and HubSpot to you know, we had a contest recently in the community where there was somebody talk you know, making GammaDex in an automation about, you know, rainfall in Uganda for your sales decks. Like, there's so many different things you can do, and that's really kind of incredible. But the the one thing to think about is you're doing it more than five times, you should automate it. So your next steps are gonna be, you know, create a template in Gamma, connect Zapier to the Gamma API like I showed you, grabbing that API key, test with one example, and just kinda iterating and improving. You can access our docs at developers.gamma.app, and that kinda has all of our technical documentation. We're also gonna include in our follow-up email application to join the ambassador community where I'm very active, and you can get assistance there of kinda making your workflows work. Yeah. Just like I was just saying. So yeah. After this workshop, like I said, more time, we're gonna have survey, some q and a responses to common questions, detailed resource email, and the application. Cool. Well, thanks everybody for joining me today. It was really great teaching you all about our API, and hope to see you soon in the community. Thank you very much.