Summary: For clients using Ziflow with the Oracle NetSuite CRM, we’ve simplified the task creation process between the two systems. You can now trigger a proof review and approval task directly in the NetSuite platform within your review workflows. Users can directly access proofs and tasks in NetSuite from a “Ziflow proof” tab.

Before you start configuring your first NetSuite flow, please visit this article and connect Netsuite to Ziflow.

Available for: Administrators on Enterprise edition.

Our Zibots allow you to trigger a flow when the following events occur on a proof:

  • New proof/version: triggers when a new proof is ready for review.

  • Decision: triggers when a reviewer makes a decision or when a decision is updated on the stage and/or proof.

  • New comment/reply: triggers when a reviewer adds a comment/reply to the proof.

  • Comment resolved: triggers when a comment is marked as resolved.

  • Comment labeled: triggers when a reviewer labels a comment.

  • Proof updated: triggers when the proof folder, setting, or custom property changes.

  • Stage updated: triggers when a stage is started or when a reviewer is added/removed.

Learn how to:

  1. Create a Webhook flow

  2. Set up Flow Event settings

  3. Configure NetSuite Zibot

  4. What happens after the NetSuite flow is started?


Create Ziflow Webhook Flow

Click on the Connect tab in the upper left corner of the screen, then click on the + Create flow button. Instead of connecting to cloud storage, select the Ziflow application.

Create Ziflow Webhook Flow

Set up Flow Event settings

The first step is selecting the event that will trigger your Zibot:

Set up Flow Event settings

Next, you will be presented with the event details page, which will vary depending on which event you select:

  1. New proof/version

  2. Decision made

  3. New comment/reply

  4. Comment resolved

  5. Comment labeled

  6. Proof updated

  7. Stage updated


New proof/version

New proof/version event settings in Ziflow
  1. Triggered by - select the type of request that will trigger the Zibot.

  2. Created in - select the Ziflow folder that this flow will monitor.

  3. Created by - select the user that will be responsible for this flow activation.


Decision made

Decision made event settings in Ziflow
  1. Triggered by decision made - select what level decision needs to be made to activate the flow.

  2. Type of decision - choose the type of decision that needs to be made to activate the flow.

  3. Created in - select the Ziflow folder that this flow will monitor.


New comment/reply added

New comment/reply added event settings in Ziflow
  1. Triggered by new comment / new reply - choose which option should activate the flow.

  2. Made by - choose if a Zibot should be activated by a specific reviewer or by anyone that adds a comment/reply.

  3. Created in - select the Ziflow folder that this flow will monitor.


Comment resolved

Comment resolved event settings in Ziflow
  1. Created in - select the Ziflow folder that this flow will monitor.


Comment labeled

Comment labeled event settings in Ziflow
  1. Comment is labeled as - select which label(s) should trigger a Zibot.

  2. Created in - select the Ziflow folder that this flow will monitor.


Proof updated

Proof updated event settings in Ziflow
  1. Triggered by - select which type of the proof updated event should trigger the Zibot

  2. Modified in - choose the Ziflow folder that this flow will monitor.


Stage updated

Stage updated event settings in Ziflow
  1. Triggered by - select which type of the stage updated event should trigger the Zibot

  2. Modified in - choose the Ziflow folder that will be monitored by this flow.


Configure NetSuite Zibot

Next, choose a Create a NetSuite task Zibot:

Configure NetSuite Zibot

Set up Webhook Zibot details:

Create a NetSuite task Zibot configuration
  1. Connection name - select the connection name that was selected during integration setup.

  2. Project name - choose in what project the task should be created.

  3. Task name - type NetSuite task name. JSONPath syntax can be used similarly to the Webhook Zibot.

  4. Status - select what the task status should be when posted to NetSuite.

  5. Constraint type - pick the constraint type.

  6. Estimated work - estimate how much time will be needed for the task.

  7. Finish no later than - pick the task deadline.

  8. Task assignee - choose task assignee.

Once you hit the Next button, Ziflow will confirm if the flow looks good. If there are no problems, name the flow and turn it on.

Name the flow and save it

What happens after the NetSuite flow is started?

When set criteria are met, and the Zibot is triggered, you will see its progress status under the flow name.

Additionally, you should also see the asset added to your NetSuite task list.

NetSuite task list

When you enter a NetSuite task, you can see all the details passed directly from Ziflow.

Task created in NetSuite with Ziflow integration

If you open the Ziflow proof tab inside the NetSuite task, you can preview the proof as you would normally do in Ziflow. The proof can be reviewed using all available Ziflow tools such as drawing markups, commenting, submitting decisions etc.

Ziflow proof displayed within NetSuite platform

Additional information:

Did this answer your question?