n8n Advanced Course (3/8) - Pinning and editing output data

00:07:08
https://www.youtube.com/watch?v=zcNB8L4_9mA

概要

TLDRIn video three of the NN Advanced Course, the focus is on two key features for enhancing workflow development: pinning data and editing output data. Pinning data enables users to save node outputs, reducing the need for repeated API calls and speeding up workflow building. It is indicated by a blue icon and is utilized only during test executions, not in production. The editing output feature allows for manual changes to the outputs of nodes, facilitating the testing of edge cases and debugging processes. The tutorial also introduces the use of Mockaroo to generate mock data, which streamlines the testing phase and saves time when building workflows.

収穫

  • 📌 Pinning data speeds up workflow building.
  • ✏️ Edit output feature allows manual adjustments.
  • ⏱️ Reduces execution time by avoiding redundant API calls.
  • 🔍 Useful for testing edge cases and debugging.
  • 🔄 Pinned data is not used in production runs.
  • 📊 Mockaroo helps generate mock data easily.
  • 📑 JSON format is essential for data integration.
  • 🔄 Reuse past execution data to fix errors quickly.
  • 🌟 Next video covers sub-workflows
  • 😃 Streamlines the testing phase in workflow development.

タイムライン

  • 00:00:00 - 00:07:08

    In this video on advanced NN course, the focus is on 'pinning data' and 'editing output data' features to enhance workflow efficiency. Pinning data enables quick access to a node's output, avoiding repeated executions that can slow down the workflow. The pinned data is only used during test executions and is indicated by a blue icon. Furthermore, the edit output feature allows manual modifications of a node's output, facilitating testing of edge cases without external calls. Techniques for using both features in conjunction with mock data tools like Mockaroo are discussed, illustrating how to efficiently create test data and troubleshoot workflows. Overall, these features aim to minimize time-consuming tasks in the testing and building phases of workflow development.

マインドマップ

ビデオQ&A

  • What is pinning data?

    Pinning data allows users to save the output of a node for quick access during workflow development.

  • How can pinning data help in workflow building?

    It helps avoid redundant external API calls and speeds up the development process.

  • What is the edit output feature?

    The edit output feature lets you manually adjust the output of a node for testing specific scenarios.

  • How do you pin data?

    You can pin data by clicking the pin icon next to a node's output.

  • Can pinned data be used in production?

    No, pinned data is only for test executions, not for production runs.

  • What is Mockaroo?

    Mockaroo is a tool that generates random mock data for testing workflows.

  • How do you edit output data?

    You can edit output data by navigating to a node's output pane and modifying the values directly.

  • Can you paste data from previous executions?

    Yes, you can copy past data from previous executions to facilitate debugging.

  • What format should mock data be in?

    The mock data should be in JSON format for easy integration into workflows.

  • What topics will be covered in the next video?

    The next video will cover sub-workflows and their appropriate usage.

ビデオをもっと見る

AIを活用したYouTubeの無料動画要約に即アクセス！
字幕
en
オートスクロール:
  • 00:00:00
    hey and welcome to video number three of
  • 00:00:03
    the advanced course for NN in this video
  • 00:00:05
    we'll be covering pinning data what it
  • 00:00:08
    is why it's useful as well as the edit
  • 00:00:11
    output data feature um both of these
  • 00:00:14
    features will come in very handy when
  • 00:00:16
    building your
  • 00:00:18
    workflows so let's talk a little bit
  • 00:00:20
    about pinning data um to speed up
  • 00:00:23
    workflow building you want to rely as
  • 00:00:25
    little as possible on external services
  • 00:00:29
    to reduce execution time as much as
  • 00:00:31
    possible every time you're re-executing
  • 00:00:34
    something you're wasting
  • 00:00:36
    time in comes in the pinning data
  • 00:00:39
    feature you can pin the output of a node
  • 00:00:42
    to make it readily accessible you can
  • 00:00:45
    use this to avoid triggering external
  • 00:00:47
    systems again like making API calls or
  • 00:00:50
    to speed up execution while building you
  • 00:00:54
    can pin data by clicking on the little
  • 00:00:56
    pin icon that you can see to the top
  • 00:00:59
    right of the
  • 00:01:00
    output for example if a part of a
  • 00:01:03
    workflow takes a few minutes to execute
  • 00:01:06
    you can just pin the final node and
  • 00:01:08
    continue building your workflow from
  • 00:01:11
    there pinned data is only used for text
  • 00:01:16
    test executions not production ones
  • 00:01:19
    where the node is always executed you
  • 00:01:22
    can see if a node has pinned data by the
  • 00:01:26
    blue icon on the
  • 00:01:28
    canvas you can keep uh one single set of
  • 00:01:32
    pin data and when the workflow is
  • 00:01:35
    activated it will just execute as
  • 00:01:37
    normal for example here the pin data
  • 00:01:42
    from the web hook node so we don't have
  • 00:01:44
    to trigger it again when building the
  • 00:01:46
    workflow which would require going into
  • 00:01:49
    a tool testing the workflow sending the
  • 00:01:52
    web hook and then building here we can
  • 00:01:55
    just start building straight
  • 00:01:58
    away another trick that we can use to
  • 00:02:01
    facilitate workflow building is to use
  • 00:02:04
    the edit output feature as its name
  • 00:02:07
    suggests this feature lets you manually
  • 00:02:09
    edit the output of a given
  • 00:02:12
    node you can see this feature uh you can
  • 00:02:15
    use this feature along with the pinned
  • 00:02:18
    data feature to tweak execution data to
  • 00:02:21
    see how it performs under specific edge
  • 00:02:26
    cases for example by setting a field to
  • 00:02:29
    null or passing a string instead of a
  • 00:02:33
    number this can save you a ton of time
  • 00:02:36
    when working with external systems
  • 00:02:38
    avoiding you uh having to recreate these
  • 00:02:41
    edge cases like making new API calls or
  • 00:02:45
    using a code or um edit Fields
  • 00:02:49
    node using the same example I can edit
  • 00:02:52
    the output web hook uh node to test
  • 00:02:56
    different sets of workflow trigger items
  • 00:03:00
    again without having to re-trigger the
  • 00:03:03
    web hook every single
  • 00:03:05
    time you can also paste in uh data from
  • 00:03:09
    a previous execution with the uh edit
  • 00:03:13
    output feature you can do this by going
  • 00:03:16
    into a previous execution navigating to
  • 00:03:20
    the output pane of the node in question
  • 00:03:24
    switching to Json View and then clicking
  • 00:03:27
    the copy button
  • 00:03:30
    um from here you can go back into your
  • 00:03:33
    workflow that you're working on edit the
  • 00:03:36
    output paste in the values and you will
  • 00:03:39
    have um that data ready to work with in
  • 00:03:42
    the workflow that you're building um
  • 00:03:44
    this is very useful when debugging a
  • 00:03:46
    workflow that might have failed and now
  • 00:03:49
    you need to go in and well make a
  • 00:03:52
    fix you can save a lot of time testing
  • 00:03:55
    workflows by using the edit output node
  • 00:03:58
    paired with a mock data tool a mock data
  • 00:04:02
    tool that I like to use is
  • 00:04:05
    mockaroo this will help you generate
  • 00:04:08
    sets of randomized information and you
  • 00:04:11
    can even uh set options for blank data
  • 00:04:15
    allowing you to generate a realistic set
  • 00:04:18
    of mock data
  • 00:04:20
    items just be sure to select the Json
  • 00:04:23
    format so you can copy paste it directly
  • 00:04:26
    into n here I have a relatively simple
  • 00:04:29
    workflow that listens to a web hook
  • 00:04:32
    edits some Fields sends a message on
  • 00:04:34
    slack and then if the ID is known
  • 00:04:38
    updates it uh in a Google Sheets a pener
  • 00:04:42
    updates so here when I'm testing the
  • 00:04:44
    workflow I can send myself a test
  • 00:04:49
    event and to avoid myself having to send
  • 00:04:53
    myself this test event multiple times
  • 00:04:55
    the first thing I can do is simply pin
  • 00:04:58
    the data so here we can see we have the
  • 00:05:01
    blue check mark which means the data is
  • 00:05:03
    pinned and if I refresh the page I can
  • 00:05:08
    see that the information is still
  • 00:05:10
    available here and I can still uh run
  • 00:05:13
    the workflow as if I had the output item
  • 00:05:17
    here now if I go into my past executions
  • 00:05:20
    I have one here that returned an error
  • 00:05:22
    so what I can do is come into to the web
  • 00:05:26
    hook node copy the output from the the
  • 00:05:29
    Json view return back to the editor
  • 00:05:33
    unpin the
  • 00:05:35
    data paste in the data from the
  • 00:05:38
    execution that had an error and save it
  • 00:05:41
    and now I
  • 00:05:42
    can keep building the workflow from that
  • 00:05:45
    state figure out why the error was
  • 00:05:48
    generated and uh Implement a fix for
  • 00:05:51
    next time last part of uh editing and
  • 00:05:55
    pinning data is to show uh how we can
  • 00:05:59
    use for example mock data so here I'm
  • 00:06:02
    going to start building a workflow and I
  • 00:06:04
    need some different information um you
  • 00:06:07
    know 10 examples of contacts so I'm
  • 00:06:10
    going to use uh a tool called mockaroo
  • 00:06:13
    and ask it to generate an ID first name
  • 00:06:16
    email gender IP address um let's say
  • 00:06:19
    that 10% of the time the email is empty
  • 00:06:24
    and here I make sure to include the Json
  • 00:06:27
    format so when I click generate data
  • 00:06:29
    sorry when I click preview I
  • 00:06:33
    have some data that I can then copy
  • 00:06:37
    paste back into
  • 00:06:40
    anyen and now I have this pin data that
  • 00:06:43
    I can start working with without having
  • 00:06:45
    to ask chat GPT or generate all of this
  • 00:06:48
    manually so this is going to save you a
  • 00:06:50
    ton of time in either building or
  • 00:06:53
    testing workflows thanks for listening
  • 00:06:55
    to the third video of the NN Advanced
  • 00:06:58
    course where we covered pinning data and
  • 00:07:00
    editing outputs in the next video we'll
  • 00:07:03
    cover subw workflows and when to use
  • 00:07:06
    them
タグ
  • pinning data
  • editing output
  • workflow building
  • NN Advanced Course
  • API calls
  • debugging
  • mock data
  • Mockaroo
  • test executions
  • sub-workflows