---
title: FAQs - Integrations
description: Check the frequently asked questions
documentId: integrations-faqs
locale: en-US
---

# FAQs

Sensedia Integrations FAQs are organized by thematic sections.
If you have a question that you believe should be included here, you can write it in the feedback field at the end of this page.

## Security and Access

<Accordion title="If I change the data of an authorization used in a deployed flow, will I need to deploy the flow again?">

Yes. You will need to redeploy the flow in the environment where the authorization data was changed for the changes to be applied.
</Accordion>


## Connectors

<Accordion title="Can I edit the data of an existing REST API connector?">

No. You will need to delete and create the REST API connector again. 
If the connector is in use, you will need to create a new connector with a new version.
</Accordion>


<Accordion title="Who can view a database connector that I created?">

Only the tenant that created the database connector (MYSQL, Oracle, PostgreSQL, etc.) can view it.
</Accordion>


<Accordion title="What is an instruction for a technical connector and how do I write it?">

**What is an instruction?**

An *instruction* is a command or query used to interact with systems or services within an integration flow.
They allow you to manipulate data or trigger operations, such as querying information, sending data, or executing specific actions, being essential for the exchange and management of information between integrated systems.

When configuring the form of a technical connector, you need to fill in the **INSTRUCTION** field according to the selected connector type. 
In this field, you will create a script using the native syntax of the protocol that the connector accesses.

<Callout type="important" title="IMPORTANT">
Most technical connectors available in Sensedia Integrations require instructions with SQL syntax.
</Callout>

**How to write an instruction?**

You can write the instruction in two ways, using [*Properties*](/docs/integrations/ipaas-legacy-expression-builder), which allow the use of environment variables and properties from previous steps in the flow:

* **Insert input attributes**: Select the desired items in Properties from the left panel.

* **Create an expression**: Combine items from Properties using the *Concat* function. 
To use it, click the **fx** button available to create expressions.

<Callout type="note" title="NOTE">
Check out more information about how to [build SQL instructions](/docs/integrations/ipaas-legacy-sql-instructions) and how to use the [Concat function](/docs/integrations/ipaas-legacy-concat) to create expressions.
</Callout>

See the videos below that demonstrate how to create a simple instruction for a MySQL connector:

* With the Concat function: 

![With the concat function](https://www.youtube.com/watch?v=zwJoaMFtoTE)

* Without the Concat function: 

![Without the concat function](https://www.youtube.com/watch?v=W0tR-Ifh3s8)

</Accordion>


## Integration Flows

<Accordion title="What is a Canvas type flow and a Diagram & Source Code type flow?">

**Canvas**

A [**Canvas**](/docs/integrations/ipaas-legacy-canvas) type flow is created in a *low-code* environment, where you develop the integration flow visually.
With the [**Flow**](/docs/integrations/ipaas-legacy-flow) graphical interface, you can build the flow by dragging and dropping elements on the screen, without the need to write code.

This type of flow allows you to easily add *steps* such as:

- [Triggers](/docs/integrations/ipaas-legacy-triggers)
- [General tools](/docs/integrations/ipaas-legacy-general-tools)
- [Connectors](/docs/integrations/ipaas-legacy-connectors)

<Callout type="important" title="IMPORTANT">
These flows have limited functionality.
</Callout>

The animation shows the process of selecting and including steps of an integration flow on the **Flow** screen:

![Flow](https://creative-ball-51b3fc85c0.media.strapiapp.com/faqs_drag_drop_72f298b5fd.gif)

<Callout type="note" title="NOTE">
Check out how to [create a Canvas (legacy) type integration flow](/docs/integrations/ipaas-legacy-create-flow).
</Callout>

**Diagram & Source Code**

A [**Diagram & Source Code**](/docs/integrations/ipaas-integrations-guide) type flow combines code usage with the *low-code* experience.
You can create flows directly in the **Diagram** tab (through forms) and then edit them in the **Source Code** tab, and vice versa.

This type of flow is ideal for more complex scenarios, where code flexibility is necessary for customizations or integrations with more detailed logic.

The animation shows how to create a **Diagram & Source Code** type flow and the functionalities of each tab:

![](https://creative-ball-51b3fc85c0.media.strapiapp.com/create_flow_2a5b9af565.gif)

<Callout type="note" title="NOTE">
Check out how to [create a Diagram & Source Code type integration flow](/docs/integrations/ipaas-flow-create).
</Callout>
</Accordion>

<Accordion title="Can I import or export integration flows?">

No. It is currently not possible to import or export integration flows.
</Accordion>


## Executions

<Accordion title="I cannot view the execution traces of a flow. What might be happening?">

If you cannot view the execution traces of a flow, it is possible that the traces feature is not enabled for your user in Access Control.

To enable trace viewing, your user must be associated with a role that has the *Observability* permission grouper selected along with the items below:


- Traces
  - Traces List
  - Traces View

The trace viewing option is only visible for executions performed after the traces feature has been enabled.

[Observability](https://creative-ball-51b3fc85c0.media.strapiapp.com/observability_traces_130f619968.png)

See how to [create a role and enable permissions in Access Control](https://docs.sensedia-eng.com/pt-BR/docs/access-control#ac-policies)
</Accordion>