diff --git a/docs/index.html b/docs/index.html index 4c6fbb339..55411c905 100644 --- a/docs/index.html +++ b/docs/index.html @@ -4179,7 +4179,11 @@

Logging

-

There are two types of logs for a Zapier app, console logs and HTTP logs. The console logs are created by your app through the use of the z.console.log method (see below for details). The HTTP logs are created automatically by Zapier whenever your app makes HTTP requests (as long as you use z.request([url], options) or shorthand request objects).

To view the logs for your application, use the zapier logs command. There are three types of logs, http (logged automatically by Zapier on HTTP requests), bundle (logged automatically on every method execution), and console (manual logs via z.console.log() statements).

For advanced logging options including only displaying the logs for a certain user or app version, look at the help for the logs command:

+

To view the logs for your application, use the zapier logs command.

There are three types of logs for a Zapier app:

    +
  • http: logged automatically by Zapier on HTTP requests
    • +
  • bundle: logged automatically on every method execution
    • +
  • console: manual logs via z.console.log() statements (see below for details)
    • +

For advanced logging options, including only displaying the logs for a certain user or app version, look at the help for the logs command:

zapier help logs
@@ -4208,7 +4212,7 @@ 
Console Logging
-

The z.console object has all the same methods and works just like the Node.js Console class - the only difference is we'll log to our distributed datastore and you can view them via zapier logs (more below).

+

The z.console object has all the same methods and works just like the Node.js Console class - the only difference is we'll log to our distributed datastore and you can view the logs via zapier logs (more below).

@@ -4264,7 +4268,7 @@

HTTP Logging

-

If you are using the z.request() shortcut that we provide - HTTP logging is handled automatically for you. For example:

+

If you are using shorthand HTTP requests or the z.request() method that we provide, HTTP logging is handled automatically for you. For example:

z.request('https://57b20fb546b57d1100a3c405.mockapi.io/api/recipes')
@@ -4276,6 +4280,15 @@ 
HTTP Logging
+
+
+

HTTP logging will often work with other methods of making requests as well, but if you're using another method and having trouble seeing logs, try using z.request().

+
+
+ +
+
+

Viewing HTTP Logs

@@ -4297,7 +4310,7 @@

Viewing HTTP Logs

-

To see detailed http logs including headers, request and response bodies, etc, do:

+

To see detailed HTTP logs, including data such as headers and request and response bodies, do:

zapier logs --type=http --detailed
diff --git a/packages/cli/README-source.md b/packages/cli/README-source.md
index 6ffabcb9c..dc09ecffa 100644
--- a/packages/cli/README-source.md
+++ b/packages/cli/README-source.md
@@ -1400,11 +1400,15 @@ See a full example with dehydration/hydration wired in correctly:
 
 ## Logging
 
-There are two types of logs for a Zapier app, console logs and HTTP logs. The console logs are created by your app through the use of the `z.console.log` method ([see below for details](#console-logging)). The HTTP logs are created automatically by Zapier whenever your app makes HTTP requests (as long as you use `z.request([url], options)` or shorthand request objects).
+To view the logs for your application, use the `zapier logs` command.
 
-To view the logs for your application, use the `zapier logs` command. There are three types of logs, `http` (logged automatically by Zapier on HTTP requests), `bundle` (logged automatically on every method execution), and `console` (manual logs via `z.console.log()` statements).
+There are three types of logs for a Zapier app:
 
-For advanced logging options including only displaying the logs for a certain user or app version, look at the help for the logs command:
+* `http`: logged automatically by Zapier on HTTP requests
+* `bundle`: logged automatically on every method execution
+* `console`: manual logs via `z.console.log()` statements ([see below for details](#console-logging))
+
+For advanced logging options, including only displaying the logs for a certain user or app version, look at the help for the logs command:
 
 ```bash
 zapier help logs
@@ -1418,7 +1422,7 @@ To manually print a log statement in your code, use `z.console.log`:
 z.console.log('Here are the input fields', bundle.inputData);
 ```
 
-The `z.console` object has all the same methods and works just like the Node.js [`Console`](https://nodejs.org/docs/latest-v6.x/api/console.html) class - the only difference is we'll log to our distributed datastore and you can view them via `zapier logs` (more below).
+The `z.console` object has all the same methods and works just like the Node.js [`Console`](https://nodejs.org/docs/latest-v14.x/api/console.html) class - the only difference is we'll log to our distributed datastore and you can view the logs via `zapier logs` (more below).
 
 ### Viewing Console Logs
 
@@ -1438,7 +1442,7 @@ zapier logs --type=bundle
 
 ### HTTP Logging
 
-If you are using the `z.request()` shortcut that we provide - HTTP logging is handled automatically for you. For example:
+If you are using [shorthand HTTP requests](#shorthand-http-requests) or the `z.request()` method that we provide, HTTP logging is handled automatically for you. For example:
 
 ```js
 z.request('https://57b20fb546b57d1100a3c405.mockapi.io/api/recipes')
@@ -1448,6 +1452,8 @@ z.request('https://57b20fb546b57d1100a3c405.mockapi.io/api/recipes')
   })
 ```
 
+HTTP logging will often work with other methods of making requests as well, but if you're using another method and having trouble seeing logs, try using `z.request()`.
+
 ### Viewing HTTP Logs
 
 To see the HTTP logs, do:
@@ -1455,7 +1461,7 @@ To see the HTTP logs, do:
 ```bash
 zapier logs --type=http
 ```
-To see detailed http logs including headers, request and response bodies, etc, do:
+To see detailed HTTP logs, including data such as headers and request and response bodies, do:
 
 ```bash
 zapier logs --type=http --detailed
diff --git a/packages/cli/README.md b/packages/cli/README.md
index 7dfa22c3e..f6fd3cdb5 100644
--- a/packages/cli/README.md
+++ b/packages/cli/README.md
@@ -2553,11 +2553,15 @@ module.exports = App;
 
 ## Logging
 
-There are two types of logs for a Zapier app, console logs and HTTP logs. The console logs are created by your app through the use of the `z.console.log` method ([see below for details](#console-logging)). The HTTP logs are created automatically by Zapier whenever your app makes HTTP requests (as long as you use `z.request([url], options)` or shorthand request objects).
+To view the logs for your application, use the `zapier logs` command.
 
-To view the logs for your application, use the `zapier logs` command. There are three types of logs, `http` (logged automatically by Zapier on HTTP requests), `bundle` (logged automatically on every method execution), and `console` (manual logs via `z.console.log()` statements).
+There are three types of logs for a Zapier app:
 
-For advanced logging options including only displaying the logs for a certain user or app version, look at the help for the logs command:
+* `http`: logged automatically by Zapier on HTTP requests
+* `bundle`: logged automatically on every method execution
+* `console`: manual logs via `z.console.log()` statements ([see below for details](#console-logging))
+
+For advanced logging options, including only displaying the logs for a certain user or app version, look at the help for the logs command:
 
 ```bash
 zapier help logs
@@ -2571,7 +2575,7 @@ To manually print a log statement in your code, use `z.console.log`:
 z.console.log('Here are the input fields', bundle.inputData);
 ```
 
-The `z.console` object has all the same methods and works just like the Node.js [`Console`](https://nodejs.org/docs/latest-v6.x/api/console.html) class - the only difference is we'll log to our distributed datastore and you can view them via `zapier logs` (more below).
+The `z.console` object has all the same methods and works just like the Node.js [`Console`](https://nodejs.org/docs/latest-v14.x/api/console.html) class - the only difference is we'll log to our distributed datastore and you can view the logs via `zapier logs` (more below).
 
 ### Viewing Console Logs
 
@@ -2591,7 +2595,7 @@ zapier logs --type=bundle
 
 ### HTTP Logging
 
-If you are using the `z.request()` shortcut that we provide - HTTP logging is handled automatically for you. For example:
+If you are using [shorthand HTTP requests](#shorthand-http-requests) or the `z.request()` method that we provide, HTTP logging is handled automatically for you. For example:
 
 ```js
 z.request('https://57b20fb546b57d1100a3c405.mockapi.io/api/recipes')
@@ -2601,6 +2605,8 @@ z.request('https://57b20fb546b57d1100a3c405.mockapi.io/api/recipes')
   })
 ```
 
+HTTP logging will often work with other methods of making requests as well, but if you're using another method and having trouble seeing logs, try using `z.request()`.
+
 ### Viewing HTTP Logs
 
 To see the HTTP logs, do:
@@ -2608,7 +2614,7 @@ To see the HTTP logs, do:
 ```bash
 zapier logs --type=http
 ```
-To see detailed http logs including headers, request and response bodies, etc, do:
+To see detailed HTTP logs, including data such as headers and request and response bodies, do:
 
 ```bash
 zapier logs --type=http --detailed
diff --git a/packages/cli/docs/index.html b/packages/cli/docs/index.html
index 4c6fbb339..55411c905 100644
--- a/packages/cli/docs/index.html
+++ b/packages/cli/docs/index.html
@@ -4179,7 +4179,11 @@ 
Logging
-

There are two types of logs for a Zapier app, console logs and HTTP logs. The console logs are created by your app through the use of the z.console.log method (see below for details). The HTTP logs are created automatically by Zapier whenever your app makes HTTP requests (as long as you use z.request([url], options) or shorthand request objects).

To view the logs for your application, use the zapier logs command. There are three types of logs, http (logged automatically by Zapier on HTTP requests), bundle (logged automatically on every method execution), and console (manual logs via z.console.log() statements).

For advanced logging options including only displaying the logs for a certain user or app version, look at the help for the logs command:

+

To view the logs for your application, use the zapier logs command.

There are three types of logs for a Zapier app:

    +
  • http: logged automatically by Zapier on HTTP requests
    • +
  • bundle: logged automatically on every method execution
    • +
  • console: manual logs via z.console.log() statements (see below for details)
    • +

For advanced logging options, including only displaying the logs for a certain user or app version, look at the help for the logs command:

zapier help logs
@@ -4208,7 +4212,7 @@ 
Console Logging
-

The z.console object has all the same methods and works just like the Node.js Console class - the only difference is we'll log to our distributed datastore and you can view them via zapier logs (more below).

+

The z.console object has all the same methods and works just like the Node.js Console class - the only difference is we'll log to our distributed datastore and you can view the logs via zapier logs (more below).

@@ -4264,7 +4268,7 @@

HTTP Logging

-

If you are using the z.request() shortcut that we provide - HTTP logging is handled automatically for you. For example:

+

If you are using shorthand HTTP requests or the z.request() method that we provide, HTTP logging is handled automatically for you. For example:

z.request('https://57b20fb546b57d1100a3c405.mockapi.io/api/recipes')
@@ -4276,6 +4280,15 @@ 
HTTP Logging
+
+
+

HTTP logging will often work with other methods of making requests as well, but if you're using another method and having trouble seeing logs, try using z.request().

+
+
+ +
+
+

Viewing HTTP Logs

@@ -4297,7 +4310,7 @@

Viewing HTTP Logs

-

To see detailed http logs including headers, request and response bodies, etc, do:

+

To see detailed HTTP logs, including data such as headers and request and response bodies, do:

zapier logs --type=http --detailed