Building Blocks

Getting started with the building blocks of Summit.

Let's learn what makes Summit apps, automations, and API's work.

Events, your building blocks

Every no-code / low-code platform has building blocks. Sometimes they are called actions, sometimes nodes, sometimes steps. Continuing this tradition of coming up with our own name for things, in Summit these are called events — named because each step is a thing that happens along the way. If you're a developer, you can think of an Event as a function.

In Summit, a chain of events is called a model. In other platforms you might call this a workflow, or a zap, or a scenario.

Working with data

All events produce data, and Summit's default format for data is JSON (JavaScript Object Notation).

To reference the data produced by an event, we use liquid syntax and refer to the title of the event. So if we have an event called "my_request", we can access its data using the expression {{ my_request }} elsewhere in our model.

🐍

The templating engine

Internally, Summit uses the Django templating engine to render your liquid syntax expressions. This means that (nearly) all of the filters and template tags that are part of the Django web framework are available to you in SEL. To learn more, check out the official documentation for variables, filters, and tags.