# Payloads count - workflow triggers **URL:** \ **Category:** Help\ **Tags:** workflow\ **Created:** [August 14, 2020, 2:55am UTC](https://forums.losant.com/t/payloads-count-workflow-triggers/3198 "2020-08-14T02:55:51Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Vander\_Maziero](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/vander_maziero/32/3428_2.png) [@Vander\_Maziero](https://forums.losant.com/u/Vander_Maziero)\ **Post date:** [August 14, 2020, 2:55am UTC](https://forums.losant.com/t/payloads-count-workflow-triggers/3198/1 "2020-08-14T02:55:51Z")
Hello, I have a question regarding the accounting of payloads, in application workflows with the exception of triggers: endpoint, timer and virtual button, the others also count payloads when they are executed, or when an execution is triggered from these triggers it is not counted a payload? Thanks ---
**Author:** ![Aidan\_Zebertavage](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/aidan_zebertavage/32/2719_2.png) [@Aidan\_Zebertavage](https://forums.losant.com/u/Aidan_Zebertavage)\ **Post date:** [August 14, 2020, 2:30pm UTC](https://forums.losant.com/t/payloads-count-workflow-triggers/3198/3 "2020-08-14T14:30:27Z")
Hi @Vander_Maziero, For your awareness, we do have updates planned to improve our documentation around this topic, but in the meantime, you can expect the following interactions to count as a payload: - A device reporting its [state](https://docs.losant.com/devices/state/) - A [command](https://docs.losant.com/devices/commands/) sent to a device - Device connections to and disconnections from the [Losant broker](https://docs.losant.com/mqtt/overview/#the-losant-message-broker) or via the REST API - Workflow [timer triggers](https://docs.losant.com/workflows/triggers/timer/) - Incoming [webhook](https://docs.losant.com/applications/webhooks/) requests - Incoming [experience endpoint](https://docs.losant.com/experiences/endpoints/) requests - Incoming [integration](https://docs.losant.com/applications/integrations/) messages - Workflow virtual buttons presses, including those triggered by an [Input Controls](https://docs.losant.com/dashboards/input-controls/) block - MQTT inbound and outbound messages (other than those listed above) As you mentioned, most of these are from Trigger Nodes. However, creating events (Event Data Nodes), data requests (HTTP Node), webhook replies (Webhook Reply Node), workflow runs triggered by other workflows (Workflow Trigger Node), and data table manipulations (Data Table Nodes) do not count as a payload. However, there are some non-trigger nodes that can generate a paylaod. For example, the Device State Node is an Output Node. Because this node reports state, and that’s one of the action that Losant’s counts as a payload, this is an example of a non-trigger node generating a payload. Is there a particular node type in your application workflow that you are concerned about impacting payload count? You can see further details regarding payload counts and usage statistics in your Organizations overview page. > **[Resource Limits](https://docs.losant.com/organizations/resource-limits/#viewing-current-usage)** > > Learn about resource limits for Sandboxes and Organizations. Thanks, @Aidan_Zebertavage ---
**Author:** ![Vander\_Maziero](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/vander_maziero/32/3428_2.png) [@Vander\_Maziero](https://forums.losant.com/u/Vander_Maziero)\ **Post date:** [August 14, 2020, 3:34pm UTC](https://forums.losant.com/t/payloads-count-workflow-triggers/3198/5 "2020-08-14T15:34:47Z")
So, if I use this flow, trigger by Device: Inactive, and create an event from that, a payload would not be counted, correct? ![image](https://us1.discourse-cdn.com/flex015/uploads/getstructure/original/2X/0/02b974c303113be078c6a8d78ae7b25e639be2ac.png) ---
**Author:** ![Aidan\_Zebertavage](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/aidan_zebertavage/32/2719_2.png) [@Aidan\_Zebertavage](https://forums.losant.com/u/Aidan_Zebertavage)\ **Post date:** [August 14, 2020, 3:59pm UTC](https://forums.losant.com/t/payloads-count-workflow-triggers/3198/7 "2020-08-14T15:59:02Z")
@Vander_Maziero, Your workflow above would increase your payload count by **one** because of the `Device: Inactive` trigger node itself, and not the `Build Event` or `Event: Create` nodes in the workflow. The Device: Inactive trigger node will create a payload that includes the date of the last state report in the data field, as well as the duration of inactivity. This payload is then used throughout the rest of the workflow to build and create your event, but those two remaining nodes will not increase your payload count, since they are ingesting and processing information off the payload generated by the Device: Inactive node. > **[Device: Inactive Trigger Node](https://docs.losant.com/workflows/triggers/on-inactivity/#payload)** > > Learn more about the Losant Device: Inactivity Trigger. Thanks, @Aidan_Zebertavage ---
**Author:** ![Vander\_Maziero](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/vander_maziero/32/3428_2.png) [@Vander\_Maziero](https://forums.losant.com/u/Vander_Maziero)\ **Post date:** [August 14, 2020, 4:53pm UTC](https://forums.losant.com/t/payloads-count-workflow-triggers/3198/9 "2020-08-14T16:53:25Z")
Thanks, @Aidan_Zebertavage So, looking at the API schema ([https://docs.losant.com/rest-api/schemas/#payload-counts](https://docs.losant.com/rest-api/schemas/#payload-counts)) that returns the payload count, what property is that payload counted in, or that payload count isn’t in the schema? ---
**Author:** ![Aidan\_Zebertavage](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/aidan_zebertavage/32/2719_2.png) [@Aidan\_Zebertavage](https://forums.losant.com/u/Aidan_Zebertavage)\ **Post date:** [August 14, 2020, 5:33pm UTC](https://forums.losant.com/t/payloads-count-workflow-triggers/3198/11 "2020-08-14T17:33:43Z")
@Vander_Maziero, The `Device: Inactive` trigger nodes payload counts are rolled into the - `timer.flow` counter. We do not separate out this particular node into its own counter. ![Screen Shot 2020-08-14 at 1.24.35 PM](https://us1.discourse-cdn.com/flex015/uploads/getstructure/original/2X/4/48ce99d2009e8a712939e4dc2768fb677b7df595.png) Thanks, @Aidan_Zebertavage ---
**Author:** ![Vander\_Maziero](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/vander_maziero/32/3428_2.png) [@Vander\_Maziero](https://forums.losant.com/u/Vander_Maziero)\ **Post date:** [August 17, 2020, 4:30pm UTC](https://forums.losant.com/t/payloads-count-workflow-triggers/3198/13 "2020-08-17T16:30:51Z")
Another question about the payload counts of the trigger nodes, I tested in the sandbox, the following flow, and noticed that the triggers Device: State and Event, are not counted in the payloads, right? ![image](https://us1.discourse-cdn.com/flex015/uploads/getstructure/original/2X/6/6bd8001ebe9ef8bdc94096d9b657bf67d784f8f8.png) Because in the payload count, the virtual button (5), the set device state by workflow (5), and the states sent via simulator (5) were counted. The other triggers are not accounted. ![image](https://us1.discourse-cdn.com/flex015/uploads/getstructure/original/2X/5/56b839e293f75b2db0e393dcd8a638a0c2f95ca7.png) ![image](https://us1.discourse-cdn.com/flex015/uploads/getstructure/original/2X/a/a6e81e7a397d0f0b5b5d94e1b11295de550b9e09.png) ---
**Author:** ![Aidan\_Zebertavage](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/aidan_zebertavage/32/2719_2.png) [@Aidan\_Zebertavage](https://forums.losant.com/u/Aidan_Zebertavage)\ **Post date:** [August 19, 2020, 2:48pm UTC](https://forums.losant.com/t/payloads-count-workflow-triggers/3198/15 "2020-08-19T14:48:15Z")
Hey @Vander_Maziero, Apologies on the delay, you are correct on both nodes, the `Device: State` trigger does not generate a payload itself. The device reporting state generates that payload, so it’s already been accounted for. The `Event: Create` node also does not generate a payload, rather it is creating an Event based on information from a previously generated payload. Thanks, @Aidan_Zebertavage