The document discusses how to build no-code applications using the Webflow CMS, Google Sheets, the Github API, and Zapier. It provides examples of CMS-driven sites that were built for internal use at Webflow and for Chance the Rapper's team. It then demonstrates how to create an applicant tracking system using these tools by building forms in Webflow, setting up Zaps to populate a Google Sheet collection, and enabling updating of applicant stages and movement of cards between columns in the CMS.

1. BEN PARKER
Forms + Zaps =
No Code Apps

2. The Webflow CMS
The CMS is a powerful tool and we’ve seen
so many great sites built with Webflow that
are powered by it. Blogs, marketing sites,
landing pages, podcast sites, real estate
listings, careers & jobs pages, and this list
could go on for a long time.

3. What unlocked the
power for me
A CMS-Driven site to organize issues
that customers are facing. It is
powered by the Webflow CMS, Google
Sheets, the Github API, and by Zapier!
Built for internal use at Webflow.
STABILIZER
A CMS-Driven site that helps fans
find songs and share them with radio
stations and digital service providers
via social media. A project for
Chance the Rapper’s team.
RAPPER RADIO

4. Applicant tracking system
home page

5. Applicant tracking system
kanban page

6. Applicant tracking system
collection fields

7. This is the most important
field in your collection

8. The stages of an applicant
in our system

9. The stages of an applicant
in our system

10. Populating the collection
using a Webflow form and a
simple three step Zap

11. ⚠
A quick note
You will need to fill out the form
you’re working with one time and
submit it before you move into
Zapier. You’ll need to do this so
Zapier can find your form and so
that you have data to work with
when building your Zaps.

12. The three step Zap to add
in new applicants

13. Add in the data to your
collection from the form

14. There are
some
required
fields when
adding and
updating a
live item
You’ll want to make
sure that draft and
archived at the bottom
of the zap are set to
no.
Draft and
Archived?
When updating a live
item you are required
to add in the item ID
and the name of the
item.
Item ID &
Name

15. The three step Zap to add
in new applicants

16. Add in the item ID so we
can use it to alter the CMS

17. Now lets work on moving
cards in between the
columns and stages

18. Any place a user would click
to take action, we use a form

19. Dynamic embeds and
some minimal code

20. Now we create a zap to
update the item

21. Now we have the required fields
to make changes in the CMS

22. Now we have the required fields
to make changes in the CMS

23. Now we change the stage from
application review to initial review

24. Now we change the success
state of the form to add some
polish to the site.

25. A default success state on a
Webflow form

26. Using a loading gif in a
success state

27. Now we add a small
snippet of custom code
and our page refreshes on
submission and our card
moves between columns

28. Now the card moves when
the user takes action!

29. Go to the next
level
You can take this to the next level by
incorporating a tool like Memberstack. With a
user system, you can even show other users
who took the action and moved an applicant!