Skip to content
This repository has been archived by the owner on Nov 29, 2024. It is now read-only.

Commit

Permalink
Merge pull request #557 from zapier/remove_redirect
Browse files Browse the repository at this point in the history
[PARTOPS-861] Remove redirect to renamed "Must have trigger and actions" doc
  • Loading branch information
michellechu77 authored Dec 11, 2023
2 parents 0550c8f + a334502 commit b594800
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 3 deletions.
4 changes: 2 additions & 2 deletions docs/_quickstart/must-have-triggers-and-actions.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
---
title: Must have triggers and actions
title: Must-have triggers and actions
order: 1
layout: post-toc
redirect_from:
Expand All @@ -20,7 +20,7 @@ table {
}
</style>

# Integration design examples
# Must-have triggers and actions

Whether you're just starting to scope out a new Zapier integration build or have successfully launched your app in the Zapier App Directory, it's helpful to know what features users find the most valuable and are the most widely used across Zapier's various [app categories](https://zapier.com/apps). Ensuring your integration covers the foundational triggers, actions, and searches applicable to your app will provide more utility to your users.

Expand Down
1 change: 0 additions & 1 deletion docs/_reference/use-cases/forms-app.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,6 @@ order: 1
layout: post-toc
redirect_from:
- /partners/integration-examples
- /quickstart/integration-design-examples
---

# Zapier integration structure for a forms app
Expand Down

0 comments on commit b594800

Please sign in to comment.