From ce2afea782655ee0ee671e4b570d32210fda1d86 Mon Sep 17 00:00:00 2001
From: Chang-Hung Liang <chang-hung.liang@zapier.com>
Date: Mon, 7 Oct 2024 17:12:27 +0800
Subject: [PATCH] Update docs

---
 docs/cli.html                               | 149 +++++++-------------
 docs/cli.md                                 |  56 ++------
 packages/cli/docs/cli.html                  | 149 +++++++-------------
 packages/cli/docs/cli.md                    |  56 ++------
 packages/cli/src/oclif/ZapierBaseCommand.js |   2 +-
 packages/cli/src/oclif/commands/invoke.js   |   1 +
 6 files changed, 120 insertions(+), 293 deletions(-)

diff --git a/docs/cli.html b/docs/cli.html
index aee092834..c24e0447b 100644
--- a/docs/cli.html
+++ b/docs/cli.html
@@ -347,20 +347,13 @@ <h2 id="build">build</h2>
       <blockquote>
 <p>Build a pushable zip from the current directory.</p>
 </blockquote><p><strong>Usage</strong>: <code>zapier build</code></p><p>This command does the following:</p><ul>
-<li><p>Creates a temporary folder</p>
-</li>
-<li><p>Copies all code into the temporary folder</p>
-</li>
-<li><p>Adds an entry point: <code>zapierwrapper.js</code></p>
-</li>
-<li><p>Generates and validates app definition.</p>
-</li>
-<li><p>Detects dependencies via browserify (optional, on by default)</p>
-</li>
-<li><p>Zips up all needed <code>.js</code> files. If you want to include more files, add a &quot;includeInBuild&quot; property (array with strings of regexp paths) to your <code>.zapierapprc</code>.</p>
-</li>
-<li><p>Moves the zip to <code>build/build.zip</code> and <code>build/source.zip</code> and deletes the temp folder</p>
-</li>
+<li>Creates a temporary folder</li>
+<li>Copies all code into the temporary folder</li>
+<li>Adds an entry point: <code>zapierwrapper.js</code></li>
+<li>Generates and validates app definition.</li>
+<li>Detects dependencies via browserify (optional, on by default)</li>
+<li>Zips up all needed <code>.js</code> files. If you want to include more files, add a &quot;includeInBuild&quot; property (array with strings of regexp paths) to your <code>.zapierapprc</code>.</li>
+<li>Moves the zip to <code>build/build.zip</code> and <code>build/source.zip</code> and deletes the temp folder</li>
 </ul><p>This command is typically followed by <code>zapier upload</code>.</p><p><strong>Flags</strong></p><ul>
 <li><code>--disable-dependency-detection</code> | Disable &quot;smart&quot; file inclusion. By default, Zapier only includes files that are required by <code>index.js</code>. If you (or your dependencies) require files dynamically (such as with <code>require(someVar)</code>), then you may see &quot;Cannot find module&quot; errors. Disabling this may make your <code>build.zip</code> too large. If that&apos;s the case, try using the <code>includeInBuild</code> option in your <code>.zapierapprc</code>. See the docs about <code>includeInBuild</code> for more info.</li>
 <li><code>-d, --debug</code> | Show extra debugging output.</li>
@@ -565,15 +558,13 @@ <h2 id="describe">describe</h2>
     <div class="col-md-5 col-sm-12 col-height  docs-primary">
       <blockquote>
 <p>Describe the current integration.</p>
-</blockquote><p><strong>Usage</strong>: <code>zapier describe</code></p><p>This command prints a human readable enumeration of your integrations&apos;s</p><p>triggers, searches, and creates as seen by Zapier. Useful to understand how your</p><p>resources convert and relate to different actions.</p><ul>
-<li><p><strong>Noun</strong>: your action&apos;s noun</p>
-</li>
-<li><p><strong>Label</strong>: your action&apos;s label</p>
-</li>
-<li><p><strong>Resource</strong>: the resource (if any) this action is tied to</p>
-</li>
-<li><p><strong>Available Methods</strong>: testable methods for this action</p>
-</li>
+</blockquote><p><strong>Usage</strong>: <code>zapier describe</code></p><p>This command prints a human readable enumeration of your integrations&apos;s
+triggers, searches, and creates as seen by Zapier. Useful to understand how your
+resources convert and relate to different actions.</p><ul>
+<li><strong>Noun</strong>: your action&apos;s noun</li>
+<li><strong>Label</strong>: your action&apos;s label</li>
+<li><strong>Resource</strong>: the resource (if any) this action is tied to</li>
+<li><strong>Available Methods</strong>: testable methods for this action</li>
 </ul><p><strong>Flags</strong></p><ul>
 <li><code>-f, --format</code> | Change the way structured data is presented. If &quot;json&quot; or &quot;raw&quot;, you can pipe the output of the command into other tools, such as jq. One of <code>[plain | json | raw | row | table]</code>. Defaults to <code>table</code>.</li>
 <li><code>-d, --debug</code> | Show extra debugging output.</li>
@@ -755,24 +746,16 @@ <h2 id="invoke">invoke</h2>
       <blockquote>
 <p>Invoke an auth operation, a trigger, or a create/search action locally.</p>
 </blockquote><p><strong>Usage</strong>: <code>zapier invoke [ACTIONTYPE] [ACTIONKEY]</code></p><p>This command emulates how Zapier production environment would invoke your integration. It runs code locally, so you can use this command to quickly test your integration without deploying it to Zapier. This is especially useful for debugging and development.</p><p>This command loads environment variables and <code>authData</code> from the <code>.env</code> file in the current directory. If you don&apos;t have an <code>.env</code> file yet, you can use the <code>zapier invoke auth start</code> command to help you initialize it, or you can manually create it.</p><p>The <code>zapier invoke auth start</code> subcommand will prompt you for the necessary auth fields and save them to the <code>.env</code> file.</p><p>Each line in the <code>.env</code> file should follow one of these formats:</p><ul>
-<li><p><code>VAR_NAME=VALUE</code> for environment variables</p>
-</li>
-<li><p><code>authData_FIELD_KEY=VALUE</code> for auth data fields</p>
-</li>
+<li><code>VAR_NAME=VALUE</code> for environment variables</li>
+<li><code>authData_FIELD_KEY=VALUE</code> for auth data fields</li>
 </ul><p>For example, a <code>.env</code> file for an OAuth2 integration might look like this:</p>
     </div>
     <div class="col-md-7 col-sm-12 col-height  docs-code">
-      <pre><code>
-CLIENT_ID=&apos;your_client_id&apos;
-
+      <pre><code>CLIENT_ID=&apos;your_client_id&apos;
 CLIENT_SECRET=&apos;your_client_secret&apos;
-
 authData_access_token=&apos;1234567890&apos;
-
 authData_refresh_token=&apos;abcdefg&apos;
-
 authData_account_name=&apos;zapier&apos;
-
 </code></pre>
     </div>
   </div>
@@ -782,23 +765,18 @@ <h2 id="invoke">invoke</h2>
       <p>To test if the auth data is correct, run either one of these:</p>
     </div>
     <div class="col-md-7 col-sm-12 col-height  docs-code">
-      <pre><code>
-zapier invoke auth test   # invokes authentication.test method
-
+      <pre><code>zapier invoke auth test   # invokes authentication.test method
 zapier invoke auth label  # invokes authentication.test and renders connection label
-
 </code></pre>
     </div>
   </div>
 </div><div class="row">
   <div class="row-height">
     <div class="col-md-5 col-sm-12 col-height  docs-primary">
-      <p>Once you have the correct auth data, you can test an trigger, a search, or a create action. For example, here&apos;s how you invoke a trigger with the key <code>new_recipe</code>:</p>
+      <p>To refresh stale auth data for OAuth2 or session auth, run <code>zapier invoke auth refresh</code>.</p><p>Once you have the correct auth data, you can test an trigger, a search, or a create action. For example, here&apos;s how you invoke a trigger with the key <code>new_recipe</code>:</p>
     </div>
     <div class="col-md-7 col-sm-12 col-height  docs-code">
-      <pre><code>
-zapier invoke trigger new_recipe
-
+      <pre><code>zapier invoke trigger new_recipe
 </code></pre>
     </div>
   </div>
@@ -806,33 +784,20 @@ <h2 id="invoke">invoke</h2>
   <div class="row-height">
     <div class="col-md-5 col-sm-12 col-height  docs-primary">
       <p>To add input data, use the <code>--inputData</code> flag. The input data can come from the command directly, a file, or stdin. See <strong>EXAMPLES</strong> below.</p><p>When you miss any command arguments, such as ACTIONTYPE or ACTIONKEY, the command will prompt you interactively. If you don&apos;t want to get interactive prompts, use the <code>--non-interactive</code> flag.</p><p>The <code>--debug</code> flag will show you the HTTP request logs and any console logs you have in your code.</p><p>The following is a non-exhaustive list of current limitations and may be supported in the future:</p><ul>
-<li><p><code>zapier invoke auth refresh</code> to refresh the auth data in <code>.env</code></p>
-</li>
-<li><p>Hook triggers, including REST hook subscribe/unsubscribe</p>
-</li>
-<li><p>Line items</p>
-</li>
-<li><p>Output hydration</p>
-</li>
-<li><p>File upload</p>
-</li>
-<li><p>Dynamic dropdown pagination</p>
-</li>
-<li><p>Function-based connection label</p>
-</li>
-<li><p>Buffered create actions</p>
-</li>
-<li><p>Search-or-create actions</p>
-</li>
-<li><p>Search-powered fields</p>
-</li>
-<li><p>Field choices</p>
-</li>
-<li><p>autoRefresh for OAuth2 and session auth</p>
-</li>
+<li>Hook triggers, including REST hook subscribe/unsubscribe</li>
+<li>Line items</li>
+<li>Output hydration</li>
+<li>File upload</li>
+<li>Dynamic dropdown pagination</li>
+<li>Function-based connection label</li>
+<li>Buffered create actions</li>
+<li>Search-or-create actions</li>
+<li>Search-powered fields</li>
+<li>Field choices</li>
+<li>autoRefresh for OAuth2 and session auth</li>
 </ul><p><strong>Arguments</strong></p><ul>
 <li><code>actionType</code> | The action type you want to invoke.</li>
-<li><code>actionKey</code> | The trigger/action key you want to invoke. If ACTIONTYPE is &quot;auth&quot;, this can be &quot;label&quot;, &quot;start&quot;, or &quot;test&quot;.</li>
+<li><code>actionKey</code> | The trigger/action key you want to invoke. If ACTIONTYPE is &quot;auth&quot;, this can be &quot;label&quot;, &quot;refresh&quot;, &quot;start&quot;, or &quot;test&quot;.</li>
 </ul><p><strong>Flags</strong></p><ul>
 <li><code>-i, --inputData</code> | The input data to pass to the action. Must be a JSON-encoded object. The data can be passed from the command directly like &apos;{&quot;key&quot;: &quot;value&quot;}&apos;, read from a file like @file.json, or read from stdin like @-.</li>
 <li><code>--isFillingDynamicDropdown</code> | Set bundle.meta.isFillingDynamicDropdown to true. Only makes sense for a polling trigger. When true in production, this poll is being used to populate a dynamic dropdown.</li>
@@ -847,6 +812,7 @@ <h2 id="invoke">invoke</h2>
 </ul><p><strong>Examples</strong></p><ul>
 <li><code>zapier invoke</code></li>
 <li><code>zapier invoke auth start</code></li>
+<li><code>zapier invoke auth refresh</code></li>
 <li><code>zapier invoke auth test</code></li>
 <li><code>zapier invoke auth label</code></li>
 <li><code>zapier invoke trigger new_recipe</code></li>
@@ -995,12 +961,9 @@ <h2 id="migrate">migrate</h2>
       <blockquote>
 <p>Migrate a percentage of users or a single user from one version of your integration to another.</p>
 </blockquote><p><strong>Usage</strong>: <code>zapier migrate FROMVERSION TOVERSION [PERCENT]</code></p><p>Start a migration to move users between different versions of your integration. You may also &quot;revert&quot; by simply swapping the from/to verion strings in the command line arguments (i.e. <code>zapier migrate 1.0.1 1.0.0</code>).</p><p><strong>Only use this command to migrate users between non-breaking versions, use <code>zapier deprecate</code> if you have breaking changes!</strong></p><p>Migration time varies based on the number of affected Zaps. Be patient and check <code>zapier jobs</code> to track the status. Or use <code>zapier history</code> if you want to see older jobs.</p><p>Since a migration is only for non-breaking changes, users are not emailed about the update/migration. It will be a transparent process for them.</p><p>We recommend migrating a small subset of users first, via the percent argument, then watching error logs of the new version for any sort of odd behavior. When you feel confident there are no bugs, go ahead and migrate everyone. If you see unexpected errors, you can revert.</p><p>You can migrate a specific user&apos;s Zaps by using <code>--user</code> (i.e. <code>zapier migrate 1.0.0 1.0.1 --user=user@example.com</code>). This will migrate Zaps that are private for that user. Zaps that are</p><ul>
-<li><p><a href="https://help.zapier.com/hc/en-us/articles/8496277647629">shared across the team</a>,</p>
-</li>
-<li><p><a href="https://help.zapier.com/hc/en-us/articles/8496326497037-Share-app-connections-with-your-team">shared app connections</a>, or</p>
-</li>
-<li><p>in a <a href="https://help.zapier.com/hc/en-us/articles/22330977078157-Collaborate-with-members-of-your-Team-or-Company-account">team/company account</a></p>
-</li>
+<li><a href="https://help.zapier.com/hc/en-us/articles/8496277647629">shared across the team</a>,</li>
+<li><a href="https://help.zapier.com/hc/en-us/articles/8496326497037-Share-app-connections-with-your-team">shared app connections</a>, or</li>
+<li>in a <a href="https://help.zapier.com/hc/en-us/articles/22330977078157-Collaborate-with-members-of-your-Team-or-Company-account">team/company account</a></li>
 </ul><p>will <strong>not</strong> be migrated.</p><p>Alternatively, you can pass the <code>--account</code> flag, (i.e. <code>zapier migrate 1.0.0 1.0.1 --account=account@example.com</code>). This will migrate all Zaps owned by the user, Private &amp; Shared, within all accounts for which the specified user is a member.</p><p><strong>The <code>--account</code> flag should be used cautiously as it can break shared Zaps for other users in Team or Enterprise accounts.</strong></p><p>You cannot pass both <code>PERCENT</code> and <code>--user</code> or <code>--account</code>.</p><p>You cannot pass both <code>--user</code> and <code>--account</code>.</p><p><strong>Arguments</strong></p><ul>
 <li>(required) <code>fromVersion</code> | The version FROM which to migrate users.</li>
 <li>(required) <code>toVersion</code> | The version TO which to migrate users.</li>
@@ -1035,14 +998,10 @@ <h2 id="promote">promote</h2>
       <blockquote>
 <p>Promote a specific version to public access.</p>
 </blockquote><p><strong>Usage</strong>: <code>zapier promote VERSION</code></p><p>Promote an integration version into production (non-private) rotation, which means new users can use this integration version.</p><ul>
-<li><p>This <strong>does</strong> mark the version as the official public version - all other versions &amp; users are grandfathered.</p>
-</li>
-<li><p>This does <strong>NOT</strong> build/upload or deploy a version to Zapier - you should <code>zapier push</code> first.</p>
-</li>
-<li><p>This does <strong>NOT</strong> move old users over to this version - <code>zapier migrate 1.0.0 1.0.1</code> does that.</p>
-</li>
-<li><p>This does <strong>NOT</strong> recommend old users stop using this version - <code>zapier deprecate 1.0.0 2017-01-01</code> does that.</p>
-</li>
+<li>This <strong>does</strong> mark the version as the official public version - all other versions &amp; users are grandfathered.</li>
+<li>This does <strong>NOT</strong> build/upload or deploy a version to Zapier - you should <code>zapier push</code> first.</li>
+<li>This does <strong>NOT</strong> move old users over to this version - <code>zapier migrate 1.0.0 1.0.1</code> does that.</li>
+<li>This does <strong>NOT</strong> recommend old users stop using this version - <code>zapier deprecate 1.0.0 2017-01-01</code> does that.</li>
 </ul><p>Promotes are an inherently safe operation for all existing users of your integration.</p><p>After a promotion, go to your developer platform to <a href="https://platform.zapier.com/manage/user-feedback#3-close-resolved-issues">close issues that were resolved</a> in the updated version.</p><p>If your integration is private and passes our integration checks, this will give you a URL to a form where you can fill in additional information for your integration to go public. After reviewing, the Zapier team will approve to make it public if there are no issues or decline with feedback.</p><p>Check <code>zapier jobs</code> to track the status of the promotion. Or use <code>zapier history</code> if you want to see older jobs.</p><p><strong>Arguments</strong></p><ul>
 <li>(required) <code>version</code> | The version you want to promote.</li>
 </ul><p><strong>Flags</strong></p><ul>
@@ -1131,10 +1090,8 @@ <h2 id="scaffold">scaffold</h2>
       <blockquote>
 <p>Add a starting trigger, create, search, or resource to your integration.</p>
 </blockquote><p><strong>Usage</strong>: <code>zapier scaffold ACTIONTYPE NOUN</code></p><p>The first argument should be one of <code>trigger|search|create|resource</code> followed by the noun that this will act on (something like &quot;contact&quot; or &quot;deal&quot;).</p><p>The scaffold command does two general things:</p><ul>
-<li><p>Creates a new file (such as <code>triggers/contact.js</code>)</p>
-</li>
-<li><p>Imports and registers it inside your <code>index.js</code></p>
-</li>
+<li>Creates a new file (such as <code>triggers/contact.js</code>)</li>
+<li>Imports and registers it inside your <code>index.js</code></li>
 </ul><p>You can mix and match several options to customize the created scaffold for your project.</p><p><strong>Arguments</strong></p><ul>
 <li>(required) <code>actionType</code> | undefined</li>
 <li>(required) <code>noun</code> | undefined</li>
@@ -1171,12 +1128,9 @@ <h2 id="teamadd">team:add</h2>
       <blockquote>
 <p>Add a team member to your integration.</p>
 </blockquote><p><strong>Usage</strong>: <code>zapier team:add EMAIL ROLE [MESSAGE]</code></p><p>These users come in three levels:</p><ul>
-<li><p><code>admin</code>, who can edit everything about the integration</p>
-</li>
-<li><p><code>collaborator</code>, who has read-only access for the app, and will receive periodic email updates. These updates include quarterly health scores and more.</p>
-</li>
-<li><p><code>subscriber</code>, who can&apos;t directly access the app, but will receive periodic email updates. These updates include quarterly health scores and more.</p>
-</li>
+<li><code>admin</code>, who can edit everything about the integration</li>
+<li><code>collaborator</code>, who has read-only access for the app, and will receive periodic email updates. These updates include quarterly health scores and more.</li>
+<li><code>subscriber</code>, who can&apos;t directly access the app, but will receive periodic email updates. These updates include quarterly health scores and more.</li>
 </ul><p>Team members can be freely added and removed.</p><p><strong>Arguments</strong></p><ul>
 <li>(required) <code>email</code> | The user to be invited. If they don&apos;t have a Zapier account, they&apos;ll be prompted to create one.</li>
 <li>(required) <code>role</code> | The level the invited team member should be at. Admins can edit everything and get email updates. Collaborators have read-access to the app and get email updates. Subscribers only get email updates.</li>
@@ -1210,12 +1164,9 @@ <h2 id="teamget">team:get</h2>
       <blockquote>
 <p>Get team members involved with your integration.</p>
 </blockquote><p><strong>Usage</strong>: <code>zapier team:get</code></p><p>These users come in three levels:</p><ul>
-<li><p><code>admin</code>, who can edit everything about the integration</p>
-</li>
-<li><p><code>collaborator</code>, who has read-only access for the app, and will receive periodic email updates. These updates include quarterly health scores and more.</p>
-</li>
-<li><p><code>subscriber</code>, who can&apos;t directly access the app, but will receive periodic email updates. These updates include quarterly health scores and more.</p>
-</li>
+<li><code>admin</code>, who can edit everything about the integration</li>
+<li><code>collaborator</code>, who has read-only access for the app, and will receive periodic email updates. These updates include quarterly health scores and more.</li>
+<li><code>subscriber</code>, who can&apos;t directly access the app, but will receive periodic email updates. These updates include quarterly health scores and more.</li>
 </ul><p>Use the <code>zapier team:add</code> and <code>zapier team:remove</code> commands to modify your team.</p><p><strong>Flags</strong></p><ul>
 <li><code>-f, --format</code> | Change the way structured data is presented. If &quot;json&quot; or &quot;raw&quot;, you can pipe the output of the command into other tools, such as jq. One of <code>[plain | json | raw | row | table]</code>. Defaults to <code>table</code>.</li>
 <li><code>-d, --debug</code> | Show extra debugging output.</li>
@@ -1241,7 +1192,9 @@ <h2 id="teamremove">team:remove</h2>
     <div class="col-md-5 col-sm-12 col-height  docs-primary">
       <blockquote>
 <p>Remove a team member from all versions of your integration.</p>
-</blockquote><p><strong>Usage</strong>: <code>zapier team:remove</code></p><p>Admins will immediately lose write access to the integration.</p><p>Collaborators will immediately lose read access to the integration.</p><p>Subscribers won&apos;t receive future email updates.</p><p><strong>Flags</strong></p><ul>
+</blockquote><p><strong>Usage</strong>: <code>zapier team:remove</code></p><p>Admins will immediately lose write access to the integration.
+Collaborators will immediately lose read access to the integration.
+Subscribers won&apos;t receive future email updates.</p><p><strong>Flags</strong></p><ul>
 <li><code>-d, --debug</code> | Show extra debugging output.</li>
 </ul><p><strong>Aliases</strong></p><ul>
 <li><code>team:delete</code></li>
diff --git a/docs/cli.md b/docs/cli.md
index 290718edf..b7e81161d 100644
--- a/docs/cli.md
+++ b/docs/cli.md
@@ -33,17 +33,11 @@ $ npm install -g zapier-platform-cli
 This command does the following:
 
 * Creates a temporary folder
-
 * Copies all code into the temporary folder
-
 * Adds an entry point: `zapierwrapper.js`
-
 * Generates and validates app definition.
-
 * Detects dependencies via browserify (optional, on by default)
-
 * Zips up all needed `.js` files. If you want to include more files, add a "includeInBuild" property (array with strings of regexp paths) to your `.zapierapprc`.
-
 * Moves the zip to `build/build.zip` and `build/source.zip` and deletes the temp folder
 
 This command is typically followed by `zapier upload`.
@@ -190,17 +184,12 @@ Do not use this if you have non-breaking changes, such as fixing help text.
 **Usage**: `zapier describe`
 
 This command prints a human readable enumeration of your integrations's
-
 triggers, searches, and creates as seen by Zapier. Useful to understand how your
-
 resources convert and relate to different actions.
 
 * **Noun**: your action's noun
-
 * **Label**: your action's label
-
 * **Resource**: the resource (if any) this action is tied to
-
 * **Available Methods**: testable methods for this action
 
 **Flags**
@@ -325,41 +314,31 @@ The `zapier invoke auth start` subcommand will prompt you for the necessary auth
 Each line in the `.env` file should follow one of these formats:
 
 * `VAR_NAME=VALUE` for environment variables
-
 * `authData_FIELD_KEY=VALUE` for auth data fields
 
 For example, a `.env` file for an OAuth2 integration might look like this:
 
 ```
-
 CLIENT_ID='your_client_id'
-
 CLIENT_SECRET='your_client_secret'
-
 authData_access_token='1234567890'
-
 authData_refresh_token='abcdefg'
-
 authData_account_name='zapier'
-
 ```
 
 To test if the auth data is correct, run either one of these:
 
 ```
-
 zapier invoke auth test   # invokes authentication.test method
-
 zapier invoke auth label  # invokes authentication.test and renders connection label
-
 ```
 
+To refresh stale auth data for OAuth2 or session auth, run `zapier invoke auth refresh`.
+
 Once you have the correct auth data, you can test an trigger, a search, or a create action. For example, here's how you invoke a trigger with the key `new_recipe`:
 
 ```
-
 zapier invoke trigger new_recipe
-
 ```
 
 To add input data, use the `--inputData` flag. The input data can come from the command directly, a file, or stdin. See **EXAMPLES** below.
@@ -370,33 +349,22 @@ The `--debug` flag will show you the HTTP request logs and any console logs you
 
 The following is a non-exhaustive list of current limitations and may be supported in the future:
 
-- `zapier invoke auth refresh` to refresh the auth data in `.env`
-
 - Hook triggers, including REST hook subscribe/unsubscribe
-
 - Line items
-
 - Output hydration
-
 - File upload
-
 - Dynamic dropdown pagination
-
 - Function-based connection label
-
 - Buffered create actions
-
 - Search-or-create actions
-
 - Search-powered fields
-
 - Field choices
-
 - autoRefresh for OAuth2 and session auth
 
+
 **Arguments**
 * `actionType` | The action type you want to invoke.
-* `actionKey` | The trigger/action key you want to invoke. If ACTIONTYPE is "auth", this can be "label", "start", or "test".
+* `actionKey` | The trigger/action key you want to invoke. If ACTIONTYPE is "auth", this can be "label", "refresh", "start", or "test".
 
 **Flags**
 * `-i, --inputData` | The input data to pass to the action. Must be a JSON-encoded object. The data can be passed from the command directly like '{"key": "value"}', read from a file like @file.json, or read from stdin like @-.
@@ -413,6 +381,7 @@ The following is a non-exhaustive list of current limitations and may be support
 **Examples**
 * `zapier invoke`
 * `zapier invoke auth start`
+* `zapier invoke auth refresh`
 * `zapier invoke auth test`
 * `zapier invoke auth label`
 * `zapier invoke trigger new_recipe`
@@ -437,6 +406,7 @@ Job times will vary as it depends on the size of the queue and how many users yo
 
 Jobs are returned from oldest to newest.
 
+
 **Flags**
 * `-f, --format` | Change the way structured data is presented. If "json" or "raw", you can pipe the output of the command into other tools, such as jq. One of `[plain | json | raw | row | table]`. Defaults to `table`.
 * `-d, --debug` | Show extra debugging output.
@@ -520,9 +490,7 @@ We recommend migrating a small subset of users first, via the percent argument,
 You can migrate a specific user's Zaps by using `--user` (i.e. `zapier migrate 1.0.0 1.0.1 --user=user@example.com`). This will migrate Zaps that are private for that user. Zaps that are
 
   - [shared across the team](https://help.zapier.com/hc/en-us/articles/8496277647629),
-
   - [shared app connections](https://help.zapier.com/hc/en-us/articles/8496326497037-Share-app-connections-with-your-team), or
-
   - in a [team/company account](https://help.zapier.com/hc/en-us/articles/22330977078157-Collaborate-with-members-of-your-Team-or-Company-account)
 
 will **not** be migrated.
@@ -561,11 +529,8 @@ You cannot pass both `--user` and `--account`.
 Promote an integration version into production (non-private) rotation, which means new users can use this integration version.
 
 * This **does** mark the version as the official public version - all other versions & users are grandfathered.
-
 * This does **NOT** build/upload or deploy a version to Zapier - you should `zapier push` first.
-
 * This does **NOT** move old users over to this version - `zapier migrate 1.0.0 1.0.1` does that.
-
 * This does **NOT** recommend old users stop using this version - `zapier deprecate 1.0.0 2017-01-01` does that.
 
 Promotes are an inherently safe operation for all existing users of your integration.
@@ -642,7 +607,6 @@ The first argument should be one of `trigger|search|create|resource` followed by
 The scaffold command does two general things:
 
 * Creates a new file (such as `triggers/contact.js`)
-
 * Imports and registers it inside your `index.js`
 
 You can mix and match several options to customize the created scaffold for your project.
@@ -675,9 +639,7 @@ You can mix and match several options to customize the created scaffold for your
 These users come in three levels:
 
   * `admin`, who can edit everything about the integration
-
   * `collaborator`, who has read-only access for the app, and will receive periodic email updates. These updates include quarterly health scores and more.
-
   * `subscriber`, who can't directly access the app, but will receive periodic email updates. These updates include quarterly health scores and more.
 
 Team members can be freely added and removed.
@@ -708,13 +670,12 @@ Team members can be freely added and removed.
 These users come in three levels:
 
   * `admin`, who can edit everything about the integration
-
   * `collaborator`, who has read-only access for the app, and will receive periodic email updates. These updates include quarterly health scores and more.
-
   * `subscriber`, who can't directly access the app, but will receive periodic email updates. These updates include quarterly health scores and more.
 
 Use the `zapier team:add` and `zapier team:remove` commands to modify your team.
 
+
 **Flags**
 * `-f, --format` | Change the way structured data is presented. If "json" or "raw", you can pipe the output of the command into other tools, such as jq. One of `[plain | json | raw | row | table]`. Defaults to `table`.
 * `-d, --debug` | Show extra debugging output.
@@ -730,9 +691,7 @@ Use the `zapier team:add` and `zapier team:remove` commands to modify your team.
 **Usage**: `zapier team:remove`
 
 Admins will immediately lose write access to the integration.
-
 Collaborators will immediately lose read access to the integration.
-
 Subscribers won't receive future email updates.
 
 **Flags**
@@ -774,6 +733,7 @@ This command sends both build/build.zip and build/source.zip to Zapier for use.
 
 Typically we recommend using `zapier push`, which does a build and upload, rather than `upload` by itself.
 
+
 **Flags**
 * `-d, --debug` | Show extra debugging output.
 
diff --git a/packages/cli/docs/cli.html b/packages/cli/docs/cli.html
index aee092834..c24e0447b 100644
--- a/packages/cli/docs/cli.html
+++ b/packages/cli/docs/cli.html
@@ -347,20 +347,13 @@ <h2 id="build">build</h2>
       <blockquote>
 <p>Build a pushable zip from the current directory.</p>
 </blockquote><p><strong>Usage</strong>: <code>zapier build</code></p><p>This command does the following:</p><ul>
-<li><p>Creates a temporary folder</p>
-</li>
-<li><p>Copies all code into the temporary folder</p>
-</li>
-<li><p>Adds an entry point: <code>zapierwrapper.js</code></p>
-</li>
-<li><p>Generates and validates app definition.</p>
-</li>
-<li><p>Detects dependencies via browserify (optional, on by default)</p>
-</li>
-<li><p>Zips up all needed <code>.js</code> files. If you want to include more files, add a &quot;includeInBuild&quot; property (array with strings of regexp paths) to your <code>.zapierapprc</code>.</p>
-</li>
-<li><p>Moves the zip to <code>build/build.zip</code> and <code>build/source.zip</code> and deletes the temp folder</p>
-</li>
+<li>Creates a temporary folder</li>
+<li>Copies all code into the temporary folder</li>
+<li>Adds an entry point: <code>zapierwrapper.js</code></li>
+<li>Generates and validates app definition.</li>
+<li>Detects dependencies via browserify (optional, on by default)</li>
+<li>Zips up all needed <code>.js</code> files. If you want to include more files, add a &quot;includeInBuild&quot; property (array with strings of regexp paths) to your <code>.zapierapprc</code>.</li>
+<li>Moves the zip to <code>build/build.zip</code> and <code>build/source.zip</code> and deletes the temp folder</li>
 </ul><p>This command is typically followed by <code>zapier upload</code>.</p><p><strong>Flags</strong></p><ul>
 <li><code>--disable-dependency-detection</code> | Disable &quot;smart&quot; file inclusion. By default, Zapier only includes files that are required by <code>index.js</code>. If you (or your dependencies) require files dynamically (such as with <code>require(someVar)</code>), then you may see &quot;Cannot find module&quot; errors. Disabling this may make your <code>build.zip</code> too large. If that&apos;s the case, try using the <code>includeInBuild</code> option in your <code>.zapierapprc</code>. See the docs about <code>includeInBuild</code> for more info.</li>
 <li><code>-d, --debug</code> | Show extra debugging output.</li>
@@ -565,15 +558,13 @@ <h2 id="describe">describe</h2>
     <div class="col-md-5 col-sm-12 col-height  docs-primary">
       <blockquote>
 <p>Describe the current integration.</p>
-</blockquote><p><strong>Usage</strong>: <code>zapier describe</code></p><p>This command prints a human readable enumeration of your integrations&apos;s</p><p>triggers, searches, and creates as seen by Zapier. Useful to understand how your</p><p>resources convert and relate to different actions.</p><ul>
-<li><p><strong>Noun</strong>: your action&apos;s noun</p>
-</li>
-<li><p><strong>Label</strong>: your action&apos;s label</p>
-</li>
-<li><p><strong>Resource</strong>: the resource (if any) this action is tied to</p>
-</li>
-<li><p><strong>Available Methods</strong>: testable methods for this action</p>
-</li>
+</blockquote><p><strong>Usage</strong>: <code>zapier describe</code></p><p>This command prints a human readable enumeration of your integrations&apos;s
+triggers, searches, and creates as seen by Zapier. Useful to understand how your
+resources convert and relate to different actions.</p><ul>
+<li><strong>Noun</strong>: your action&apos;s noun</li>
+<li><strong>Label</strong>: your action&apos;s label</li>
+<li><strong>Resource</strong>: the resource (if any) this action is tied to</li>
+<li><strong>Available Methods</strong>: testable methods for this action</li>
 </ul><p><strong>Flags</strong></p><ul>
 <li><code>-f, --format</code> | Change the way structured data is presented. If &quot;json&quot; or &quot;raw&quot;, you can pipe the output of the command into other tools, such as jq. One of <code>[plain | json | raw | row | table]</code>. Defaults to <code>table</code>.</li>
 <li><code>-d, --debug</code> | Show extra debugging output.</li>
@@ -755,24 +746,16 @@ <h2 id="invoke">invoke</h2>
       <blockquote>
 <p>Invoke an auth operation, a trigger, or a create/search action locally.</p>
 </blockquote><p><strong>Usage</strong>: <code>zapier invoke [ACTIONTYPE] [ACTIONKEY]</code></p><p>This command emulates how Zapier production environment would invoke your integration. It runs code locally, so you can use this command to quickly test your integration without deploying it to Zapier. This is especially useful for debugging and development.</p><p>This command loads environment variables and <code>authData</code> from the <code>.env</code> file in the current directory. If you don&apos;t have an <code>.env</code> file yet, you can use the <code>zapier invoke auth start</code> command to help you initialize it, or you can manually create it.</p><p>The <code>zapier invoke auth start</code> subcommand will prompt you for the necessary auth fields and save them to the <code>.env</code> file.</p><p>Each line in the <code>.env</code> file should follow one of these formats:</p><ul>
-<li><p><code>VAR_NAME=VALUE</code> for environment variables</p>
-</li>
-<li><p><code>authData_FIELD_KEY=VALUE</code> for auth data fields</p>
-</li>
+<li><code>VAR_NAME=VALUE</code> for environment variables</li>
+<li><code>authData_FIELD_KEY=VALUE</code> for auth data fields</li>
 </ul><p>For example, a <code>.env</code> file for an OAuth2 integration might look like this:</p>
     </div>
     <div class="col-md-7 col-sm-12 col-height  docs-code">
-      <pre><code>
-CLIENT_ID=&apos;your_client_id&apos;
-
+      <pre><code>CLIENT_ID=&apos;your_client_id&apos;
 CLIENT_SECRET=&apos;your_client_secret&apos;
-
 authData_access_token=&apos;1234567890&apos;
-
 authData_refresh_token=&apos;abcdefg&apos;
-
 authData_account_name=&apos;zapier&apos;
-
 </code></pre>
     </div>
   </div>
@@ -782,23 +765,18 @@ <h2 id="invoke">invoke</h2>
       <p>To test if the auth data is correct, run either one of these:</p>
     </div>
     <div class="col-md-7 col-sm-12 col-height  docs-code">
-      <pre><code>
-zapier invoke auth test   # invokes authentication.test method
-
+      <pre><code>zapier invoke auth test   # invokes authentication.test method
 zapier invoke auth label  # invokes authentication.test and renders connection label
-
 </code></pre>
     </div>
   </div>
 </div><div class="row">
   <div class="row-height">
     <div class="col-md-5 col-sm-12 col-height  docs-primary">
-      <p>Once you have the correct auth data, you can test an trigger, a search, or a create action. For example, here&apos;s how you invoke a trigger with the key <code>new_recipe</code>:</p>
+      <p>To refresh stale auth data for OAuth2 or session auth, run <code>zapier invoke auth refresh</code>.</p><p>Once you have the correct auth data, you can test an trigger, a search, or a create action. For example, here&apos;s how you invoke a trigger with the key <code>new_recipe</code>:</p>
     </div>
     <div class="col-md-7 col-sm-12 col-height  docs-code">
-      <pre><code>
-zapier invoke trigger new_recipe
-
+      <pre><code>zapier invoke trigger new_recipe
 </code></pre>
     </div>
   </div>
@@ -806,33 +784,20 @@ <h2 id="invoke">invoke</h2>
   <div class="row-height">
     <div class="col-md-5 col-sm-12 col-height  docs-primary">
       <p>To add input data, use the <code>--inputData</code> flag. The input data can come from the command directly, a file, or stdin. See <strong>EXAMPLES</strong> below.</p><p>When you miss any command arguments, such as ACTIONTYPE or ACTIONKEY, the command will prompt you interactively. If you don&apos;t want to get interactive prompts, use the <code>--non-interactive</code> flag.</p><p>The <code>--debug</code> flag will show you the HTTP request logs and any console logs you have in your code.</p><p>The following is a non-exhaustive list of current limitations and may be supported in the future:</p><ul>
-<li><p><code>zapier invoke auth refresh</code> to refresh the auth data in <code>.env</code></p>
-</li>
-<li><p>Hook triggers, including REST hook subscribe/unsubscribe</p>
-</li>
-<li><p>Line items</p>
-</li>
-<li><p>Output hydration</p>
-</li>
-<li><p>File upload</p>
-</li>
-<li><p>Dynamic dropdown pagination</p>
-</li>
-<li><p>Function-based connection label</p>
-</li>
-<li><p>Buffered create actions</p>
-</li>
-<li><p>Search-or-create actions</p>
-</li>
-<li><p>Search-powered fields</p>
-</li>
-<li><p>Field choices</p>
-</li>
-<li><p>autoRefresh for OAuth2 and session auth</p>
-</li>
+<li>Hook triggers, including REST hook subscribe/unsubscribe</li>
+<li>Line items</li>
+<li>Output hydration</li>
+<li>File upload</li>
+<li>Dynamic dropdown pagination</li>
+<li>Function-based connection label</li>
+<li>Buffered create actions</li>
+<li>Search-or-create actions</li>
+<li>Search-powered fields</li>
+<li>Field choices</li>
+<li>autoRefresh for OAuth2 and session auth</li>
 </ul><p><strong>Arguments</strong></p><ul>
 <li><code>actionType</code> | The action type you want to invoke.</li>
-<li><code>actionKey</code> | The trigger/action key you want to invoke. If ACTIONTYPE is &quot;auth&quot;, this can be &quot;label&quot;, &quot;start&quot;, or &quot;test&quot;.</li>
+<li><code>actionKey</code> | The trigger/action key you want to invoke. If ACTIONTYPE is &quot;auth&quot;, this can be &quot;label&quot;, &quot;refresh&quot;, &quot;start&quot;, or &quot;test&quot;.</li>
 </ul><p><strong>Flags</strong></p><ul>
 <li><code>-i, --inputData</code> | The input data to pass to the action. Must be a JSON-encoded object. The data can be passed from the command directly like &apos;{&quot;key&quot;: &quot;value&quot;}&apos;, read from a file like @file.json, or read from stdin like @-.</li>
 <li><code>--isFillingDynamicDropdown</code> | Set bundle.meta.isFillingDynamicDropdown to true. Only makes sense for a polling trigger. When true in production, this poll is being used to populate a dynamic dropdown.</li>
@@ -847,6 +812,7 @@ <h2 id="invoke">invoke</h2>
 </ul><p><strong>Examples</strong></p><ul>
 <li><code>zapier invoke</code></li>
 <li><code>zapier invoke auth start</code></li>
+<li><code>zapier invoke auth refresh</code></li>
 <li><code>zapier invoke auth test</code></li>
 <li><code>zapier invoke auth label</code></li>
 <li><code>zapier invoke trigger new_recipe</code></li>
@@ -995,12 +961,9 @@ <h2 id="migrate">migrate</h2>
       <blockquote>
 <p>Migrate a percentage of users or a single user from one version of your integration to another.</p>
 </blockquote><p><strong>Usage</strong>: <code>zapier migrate FROMVERSION TOVERSION [PERCENT]</code></p><p>Start a migration to move users between different versions of your integration. You may also &quot;revert&quot; by simply swapping the from/to verion strings in the command line arguments (i.e. <code>zapier migrate 1.0.1 1.0.0</code>).</p><p><strong>Only use this command to migrate users between non-breaking versions, use <code>zapier deprecate</code> if you have breaking changes!</strong></p><p>Migration time varies based on the number of affected Zaps. Be patient and check <code>zapier jobs</code> to track the status. Or use <code>zapier history</code> if you want to see older jobs.</p><p>Since a migration is only for non-breaking changes, users are not emailed about the update/migration. It will be a transparent process for them.</p><p>We recommend migrating a small subset of users first, via the percent argument, then watching error logs of the new version for any sort of odd behavior. When you feel confident there are no bugs, go ahead and migrate everyone. If you see unexpected errors, you can revert.</p><p>You can migrate a specific user&apos;s Zaps by using <code>--user</code> (i.e. <code>zapier migrate 1.0.0 1.0.1 --user=user@example.com</code>). This will migrate Zaps that are private for that user. Zaps that are</p><ul>
-<li><p><a href="https://help.zapier.com/hc/en-us/articles/8496277647629">shared across the team</a>,</p>
-</li>
-<li><p><a href="https://help.zapier.com/hc/en-us/articles/8496326497037-Share-app-connections-with-your-team">shared app connections</a>, or</p>
-</li>
-<li><p>in a <a href="https://help.zapier.com/hc/en-us/articles/22330977078157-Collaborate-with-members-of-your-Team-or-Company-account">team/company account</a></p>
-</li>
+<li><a href="https://help.zapier.com/hc/en-us/articles/8496277647629">shared across the team</a>,</li>
+<li><a href="https://help.zapier.com/hc/en-us/articles/8496326497037-Share-app-connections-with-your-team">shared app connections</a>, or</li>
+<li>in a <a href="https://help.zapier.com/hc/en-us/articles/22330977078157-Collaborate-with-members-of-your-Team-or-Company-account">team/company account</a></li>
 </ul><p>will <strong>not</strong> be migrated.</p><p>Alternatively, you can pass the <code>--account</code> flag, (i.e. <code>zapier migrate 1.0.0 1.0.1 --account=account@example.com</code>). This will migrate all Zaps owned by the user, Private &amp; Shared, within all accounts for which the specified user is a member.</p><p><strong>The <code>--account</code> flag should be used cautiously as it can break shared Zaps for other users in Team or Enterprise accounts.</strong></p><p>You cannot pass both <code>PERCENT</code> and <code>--user</code> or <code>--account</code>.</p><p>You cannot pass both <code>--user</code> and <code>--account</code>.</p><p><strong>Arguments</strong></p><ul>
 <li>(required) <code>fromVersion</code> | The version FROM which to migrate users.</li>
 <li>(required) <code>toVersion</code> | The version TO which to migrate users.</li>
@@ -1035,14 +998,10 @@ <h2 id="promote">promote</h2>
       <blockquote>
 <p>Promote a specific version to public access.</p>
 </blockquote><p><strong>Usage</strong>: <code>zapier promote VERSION</code></p><p>Promote an integration version into production (non-private) rotation, which means new users can use this integration version.</p><ul>
-<li><p>This <strong>does</strong> mark the version as the official public version - all other versions &amp; users are grandfathered.</p>
-</li>
-<li><p>This does <strong>NOT</strong> build/upload or deploy a version to Zapier - you should <code>zapier push</code> first.</p>
-</li>
-<li><p>This does <strong>NOT</strong> move old users over to this version - <code>zapier migrate 1.0.0 1.0.1</code> does that.</p>
-</li>
-<li><p>This does <strong>NOT</strong> recommend old users stop using this version - <code>zapier deprecate 1.0.0 2017-01-01</code> does that.</p>
-</li>
+<li>This <strong>does</strong> mark the version as the official public version - all other versions &amp; users are grandfathered.</li>
+<li>This does <strong>NOT</strong> build/upload or deploy a version to Zapier - you should <code>zapier push</code> first.</li>
+<li>This does <strong>NOT</strong> move old users over to this version - <code>zapier migrate 1.0.0 1.0.1</code> does that.</li>
+<li>This does <strong>NOT</strong> recommend old users stop using this version - <code>zapier deprecate 1.0.0 2017-01-01</code> does that.</li>
 </ul><p>Promotes are an inherently safe operation for all existing users of your integration.</p><p>After a promotion, go to your developer platform to <a href="https://platform.zapier.com/manage/user-feedback#3-close-resolved-issues">close issues that were resolved</a> in the updated version.</p><p>If your integration is private and passes our integration checks, this will give you a URL to a form where you can fill in additional information for your integration to go public. After reviewing, the Zapier team will approve to make it public if there are no issues or decline with feedback.</p><p>Check <code>zapier jobs</code> to track the status of the promotion. Or use <code>zapier history</code> if you want to see older jobs.</p><p><strong>Arguments</strong></p><ul>
 <li>(required) <code>version</code> | The version you want to promote.</li>
 </ul><p><strong>Flags</strong></p><ul>
@@ -1131,10 +1090,8 @@ <h2 id="scaffold">scaffold</h2>
       <blockquote>
 <p>Add a starting trigger, create, search, or resource to your integration.</p>
 </blockquote><p><strong>Usage</strong>: <code>zapier scaffold ACTIONTYPE NOUN</code></p><p>The first argument should be one of <code>trigger|search|create|resource</code> followed by the noun that this will act on (something like &quot;contact&quot; or &quot;deal&quot;).</p><p>The scaffold command does two general things:</p><ul>
-<li><p>Creates a new file (such as <code>triggers/contact.js</code>)</p>
-</li>
-<li><p>Imports and registers it inside your <code>index.js</code></p>
-</li>
+<li>Creates a new file (such as <code>triggers/contact.js</code>)</li>
+<li>Imports and registers it inside your <code>index.js</code></li>
 </ul><p>You can mix and match several options to customize the created scaffold for your project.</p><p><strong>Arguments</strong></p><ul>
 <li>(required) <code>actionType</code> | undefined</li>
 <li>(required) <code>noun</code> | undefined</li>
@@ -1171,12 +1128,9 @@ <h2 id="teamadd">team:add</h2>
       <blockquote>
 <p>Add a team member to your integration.</p>
 </blockquote><p><strong>Usage</strong>: <code>zapier team:add EMAIL ROLE [MESSAGE]</code></p><p>These users come in three levels:</p><ul>
-<li><p><code>admin</code>, who can edit everything about the integration</p>
-</li>
-<li><p><code>collaborator</code>, who has read-only access for the app, and will receive periodic email updates. These updates include quarterly health scores and more.</p>
-</li>
-<li><p><code>subscriber</code>, who can&apos;t directly access the app, but will receive periodic email updates. These updates include quarterly health scores and more.</p>
-</li>
+<li><code>admin</code>, who can edit everything about the integration</li>
+<li><code>collaborator</code>, who has read-only access for the app, and will receive periodic email updates. These updates include quarterly health scores and more.</li>
+<li><code>subscriber</code>, who can&apos;t directly access the app, but will receive periodic email updates. These updates include quarterly health scores and more.</li>
 </ul><p>Team members can be freely added and removed.</p><p><strong>Arguments</strong></p><ul>
 <li>(required) <code>email</code> | The user to be invited. If they don&apos;t have a Zapier account, they&apos;ll be prompted to create one.</li>
 <li>(required) <code>role</code> | The level the invited team member should be at. Admins can edit everything and get email updates. Collaborators have read-access to the app and get email updates. Subscribers only get email updates.</li>
@@ -1210,12 +1164,9 @@ <h2 id="teamget">team:get</h2>
       <blockquote>
 <p>Get team members involved with your integration.</p>
 </blockquote><p><strong>Usage</strong>: <code>zapier team:get</code></p><p>These users come in three levels:</p><ul>
-<li><p><code>admin</code>, who can edit everything about the integration</p>
-</li>
-<li><p><code>collaborator</code>, who has read-only access for the app, and will receive periodic email updates. These updates include quarterly health scores and more.</p>
-</li>
-<li><p><code>subscriber</code>, who can&apos;t directly access the app, but will receive periodic email updates. These updates include quarterly health scores and more.</p>
-</li>
+<li><code>admin</code>, who can edit everything about the integration</li>
+<li><code>collaborator</code>, who has read-only access for the app, and will receive periodic email updates. These updates include quarterly health scores and more.</li>
+<li><code>subscriber</code>, who can&apos;t directly access the app, but will receive periodic email updates. These updates include quarterly health scores and more.</li>
 </ul><p>Use the <code>zapier team:add</code> and <code>zapier team:remove</code> commands to modify your team.</p><p><strong>Flags</strong></p><ul>
 <li><code>-f, --format</code> | Change the way structured data is presented. If &quot;json&quot; or &quot;raw&quot;, you can pipe the output of the command into other tools, such as jq. One of <code>[plain | json | raw | row | table]</code>. Defaults to <code>table</code>.</li>
 <li><code>-d, --debug</code> | Show extra debugging output.</li>
@@ -1241,7 +1192,9 @@ <h2 id="teamremove">team:remove</h2>
     <div class="col-md-5 col-sm-12 col-height  docs-primary">
       <blockquote>
 <p>Remove a team member from all versions of your integration.</p>
-</blockquote><p><strong>Usage</strong>: <code>zapier team:remove</code></p><p>Admins will immediately lose write access to the integration.</p><p>Collaborators will immediately lose read access to the integration.</p><p>Subscribers won&apos;t receive future email updates.</p><p><strong>Flags</strong></p><ul>
+</blockquote><p><strong>Usage</strong>: <code>zapier team:remove</code></p><p>Admins will immediately lose write access to the integration.
+Collaborators will immediately lose read access to the integration.
+Subscribers won&apos;t receive future email updates.</p><p><strong>Flags</strong></p><ul>
 <li><code>-d, --debug</code> | Show extra debugging output.</li>
 </ul><p><strong>Aliases</strong></p><ul>
 <li><code>team:delete</code></li>
diff --git a/packages/cli/docs/cli.md b/packages/cli/docs/cli.md
index 290718edf..b7e81161d 100644
--- a/packages/cli/docs/cli.md
+++ b/packages/cli/docs/cli.md
@@ -33,17 +33,11 @@ $ npm install -g zapier-platform-cli
 This command does the following:
 
 * Creates a temporary folder
-
 * Copies all code into the temporary folder
-
 * Adds an entry point: `zapierwrapper.js`
-
 * Generates and validates app definition.
-
 * Detects dependencies via browserify (optional, on by default)
-
 * Zips up all needed `.js` files. If you want to include more files, add a "includeInBuild" property (array with strings of regexp paths) to your `.zapierapprc`.
-
 * Moves the zip to `build/build.zip` and `build/source.zip` and deletes the temp folder
 
 This command is typically followed by `zapier upload`.
@@ -190,17 +184,12 @@ Do not use this if you have non-breaking changes, such as fixing help text.
 **Usage**: `zapier describe`
 
 This command prints a human readable enumeration of your integrations's
-
 triggers, searches, and creates as seen by Zapier. Useful to understand how your
-
 resources convert and relate to different actions.
 
 * **Noun**: your action's noun
-
 * **Label**: your action's label
-
 * **Resource**: the resource (if any) this action is tied to
-
 * **Available Methods**: testable methods for this action
 
 **Flags**
@@ -325,41 +314,31 @@ The `zapier invoke auth start` subcommand will prompt you for the necessary auth
 Each line in the `.env` file should follow one of these formats:
 
 * `VAR_NAME=VALUE` for environment variables
-
 * `authData_FIELD_KEY=VALUE` for auth data fields
 
 For example, a `.env` file for an OAuth2 integration might look like this:
 
 ```
-
 CLIENT_ID='your_client_id'
-
 CLIENT_SECRET='your_client_secret'
-
 authData_access_token='1234567890'
-
 authData_refresh_token='abcdefg'
-
 authData_account_name='zapier'
-
 ```
 
 To test if the auth data is correct, run either one of these:
 
 ```
-
 zapier invoke auth test   # invokes authentication.test method
-
 zapier invoke auth label  # invokes authentication.test and renders connection label
-
 ```
 
+To refresh stale auth data for OAuth2 or session auth, run `zapier invoke auth refresh`.
+
 Once you have the correct auth data, you can test an trigger, a search, or a create action. For example, here's how you invoke a trigger with the key `new_recipe`:
 
 ```
-
 zapier invoke trigger new_recipe
-
 ```
 
 To add input data, use the `--inputData` flag. The input data can come from the command directly, a file, or stdin. See **EXAMPLES** below.
@@ -370,33 +349,22 @@ The `--debug` flag will show you the HTTP request logs and any console logs you
 
 The following is a non-exhaustive list of current limitations and may be supported in the future:
 
-- `zapier invoke auth refresh` to refresh the auth data in `.env`
-
 - Hook triggers, including REST hook subscribe/unsubscribe
-
 - Line items
-
 - Output hydration
-
 - File upload
-
 - Dynamic dropdown pagination
-
 - Function-based connection label
-
 - Buffered create actions
-
 - Search-or-create actions
-
 - Search-powered fields
-
 - Field choices
-
 - autoRefresh for OAuth2 and session auth
 
+
 **Arguments**
 * `actionType` | The action type you want to invoke.
-* `actionKey` | The trigger/action key you want to invoke. If ACTIONTYPE is "auth", this can be "label", "start", or "test".
+* `actionKey` | The trigger/action key you want to invoke. If ACTIONTYPE is "auth", this can be "label", "refresh", "start", or "test".
 
 **Flags**
 * `-i, --inputData` | The input data to pass to the action. Must be a JSON-encoded object. The data can be passed from the command directly like '{"key": "value"}', read from a file like @file.json, or read from stdin like @-.
@@ -413,6 +381,7 @@ The following is a non-exhaustive list of current limitations and may be support
 **Examples**
 * `zapier invoke`
 * `zapier invoke auth start`
+* `zapier invoke auth refresh`
 * `zapier invoke auth test`
 * `zapier invoke auth label`
 * `zapier invoke trigger new_recipe`
@@ -437,6 +406,7 @@ Job times will vary as it depends on the size of the queue and how many users yo
 
 Jobs are returned from oldest to newest.
 
+
 **Flags**
 * `-f, --format` | Change the way structured data is presented. If "json" or "raw", you can pipe the output of the command into other tools, such as jq. One of `[plain | json | raw | row | table]`. Defaults to `table`.
 * `-d, --debug` | Show extra debugging output.
@@ -520,9 +490,7 @@ We recommend migrating a small subset of users first, via the percent argument,
 You can migrate a specific user's Zaps by using `--user` (i.e. `zapier migrate 1.0.0 1.0.1 --user=user@example.com`). This will migrate Zaps that are private for that user. Zaps that are
 
   - [shared across the team](https://help.zapier.com/hc/en-us/articles/8496277647629),
-
   - [shared app connections](https://help.zapier.com/hc/en-us/articles/8496326497037-Share-app-connections-with-your-team), or
-
   - in a [team/company account](https://help.zapier.com/hc/en-us/articles/22330977078157-Collaborate-with-members-of-your-Team-or-Company-account)
 
 will **not** be migrated.
@@ -561,11 +529,8 @@ You cannot pass both `--user` and `--account`.
 Promote an integration version into production (non-private) rotation, which means new users can use this integration version.
 
 * This **does** mark the version as the official public version - all other versions & users are grandfathered.
-
 * This does **NOT** build/upload or deploy a version to Zapier - you should `zapier push` first.
-
 * This does **NOT** move old users over to this version - `zapier migrate 1.0.0 1.0.1` does that.
-
 * This does **NOT** recommend old users stop using this version - `zapier deprecate 1.0.0 2017-01-01` does that.
 
 Promotes are an inherently safe operation for all existing users of your integration.
@@ -642,7 +607,6 @@ The first argument should be one of `trigger|search|create|resource` followed by
 The scaffold command does two general things:
 
 * Creates a new file (such as `triggers/contact.js`)
-
 * Imports and registers it inside your `index.js`
 
 You can mix and match several options to customize the created scaffold for your project.
@@ -675,9 +639,7 @@ You can mix and match several options to customize the created scaffold for your
 These users come in three levels:
 
   * `admin`, who can edit everything about the integration
-
   * `collaborator`, who has read-only access for the app, and will receive periodic email updates. These updates include quarterly health scores and more.
-
   * `subscriber`, who can't directly access the app, but will receive periodic email updates. These updates include quarterly health scores and more.
 
 Team members can be freely added and removed.
@@ -708,13 +670,12 @@ Team members can be freely added and removed.
 These users come in three levels:
 
   * `admin`, who can edit everything about the integration
-
   * `collaborator`, who has read-only access for the app, and will receive periodic email updates. These updates include quarterly health scores and more.
-
   * `subscriber`, who can't directly access the app, but will receive periodic email updates. These updates include quarterly health scores and more.
 
 Use the `zapier team:add` and `zapier team:remove` commands to modify your team.
 
+
 **Flags**
 * `-f, --format` | Change the way structured data is presented. If "json" or "raw", you can pipe the output of the command into other tools, such as jq. One of `[plain | json | raw | row | table]`. Defaults to `table`.
 * `-d, --debug` | Show extra debugging output.
@@ -730,9 +691,7 @@ Use the `zapier team:add` and `zapier team:remove` commands to modify your team.
 **Usage**: `zapier team:remove`
 
 Admins will immediately lose write access to the integration.
-
 Collaborators will immediately lose read access to the integration.
-
 Subscribers won't receive future email updates.
 
 **Flags**
@@ -774,6 +733,7 @@ This command sends both build/build.zip and build/source.zip to Zapier for use.
 
 Typically we recommend using `zapier push`, which does a build and upload, rather than `upload` by itself.
 
+
 **Flags**
 * `-d, --debug` | Show extra debugging output.
 
diff --git a/packages/cli/src/oclif/ZapierBaseCommand.js b/packages/cli/src/oclif/ZapierBaseCommand.js
index 3025c9c06..7c60f954d 100644
--- a/packages/cli/src/oclif/ZapierBaseCommand.js
+++ b/packages/cli/src/oclif/ZapierBaseCommand.js
@@ -304,7 +304,7 @@ class ZapierBaseCommand extends Command {
         )
         .filter(Boolean);
 
-    const descriptionParts = this.description.split('\n').filter(Boolean);
+    const descriptionParts = this.description.split('\n\n').filter(Boolean);
     const blurb = descriptionParts[0];
     const lengthyDescription = colors.stripColors(
       descriptionParts.length > 1 ? descriptionParts.slice(1).join('\n\n') : ''
diff --git a/packages/cli/src/oclif/commands/invoke.js b/packages/cli/src/oclif/commands/invoke.js
index 6d2a490ce..2a9b0f352 100644
--- a/packages/cli/src/oclif/commands/invoke.js
+++ b/packages/cli/src/oclif/commands/invoke.js
@@ -1151,6 +1151,7 @@ InvokeCommand.args = [
 InvokeCommand.examples = [
   'zapier invoke',
   'zapier invoke auth start',
+  'zapier invoke auth refresh',
   'zapier invoke auth test',
   'zapier invoke auth label',
   'zapier invoke trigger new_recipe',