Connect Tracy at Qode to Power Automate and Dynamics 365

Tracy at Qode is a custom connector for Power Automate, which is where Dynamics 365 workflows live. A Power Platform admin imports it once. After that, anyone who builds flows can invite people to an interview and read what came of it.

What you get

Who does what

Admin: a Power Platform admin, someone who can make custom connectors in your Power Platform environment. They import the connector once and check it by signing in. These are the steps marked Admin.
Maker: anyone who builds flows in Power Automate or Dynamics 365. They use the actions below in their flows. These are the steps marked Maker.

If you are both, do every step in order.

Four actions a flow can use

List interviews: lists your interviews. It also fills the interview dropdown of Invite participant.
Invite participant: invites one person to an interview. You pick the interview and give an email, and may add a reference of your own, such as a record ID. Tracy emails them their personal link.
Get results: reads the results of one person, newest interview session first. It needs the person's ID, which Invite participant and List events both return. A session has no write-up until its report is ready.
List events: lists what has happened in your interviews, such as a result becoming ready. Event type narrows the list and Limit caps it, from 1 to 100.

The connector has no triggers, so a flow cannot start the moment an interview finishes. A flow that has to react to a finished interview runs on a Recurrence, lists the events of type result.ready with List events, and tells the ones it has handled apart by each event's id.

Dynamics 365 workflows are Power Automate flows, so the same connector serves both. The example flow below starts from a Dynamics 365 contact.

Before you start

A Tracy at Qode account, the one whose interviews the flows should work with, and an interview in it. If you are signed out, you are sent to sign in first.
A Power Platform environment where the admin can make custom connectors and where makers can build flows.
The connector file, tracy.swagger.json, from the integrations/power-platform folder of the Tracy at Qode project.

Steps

Admin: Open make.powerautomate.com, pick the environment, and open Custom connectors (under Data, or under More then Discover all).
Admin: Choose New custom connector, then Import an OpenAPI file. Name it Tracy at Qode and choose tracy.swagger.json.
Admin: On General, check that the scheme is HTTPS, the host is tracyinterview.ai and the base URL is /.
Admin: On Definition, check that the four actions are there. Open any of them and check that the X-Tracy-Client header has the default dynamics365 and the visibility internal.
Admin: Choose Create connector.
Admin: Open the Test tab of the connector and make a New connection. A Tracy at Qode sign-in window opens. If you are signed out, sign in there, as the account whose interviews the flows should work with.
Admin: Approve access: click Allow. The window closes and the connection is made. Then run List interviews. A 200 answer with your interviews proves the sign-in, the host and the header at once.
Maker: In Power Automate, make a flow. The example flow invites each new contact in Dynamics 365 to an interview. Start it with the Microsoft Dataverse trigger When a row is added, modified or deleted. Set Change type to Added, Table name to Contacts and Scope to Organization.
Maker: Add the action Tracy at Qode, then Invite participant. If Power Automate asks for a connection, make one the way the admin did on the Test tab: sign in to Tracy at Qode in the window that opens, then click Allow. In Interview, pick one from the dropdown, which is List interviews.
Maker: In Email, open the Expression tab and enter:concat(triggerOutputs()?['body/fullname'], ' <', triggerOutputs()?['body/emailaddress1'], '>')With a full name this reads Ada Lovelace <ada@example.com>. With no name, Tracy greets the person by the start of the address. Keep each value on one line: a line break would invite a second person.
Maker: Under Show advanced options, set Reference to the contact's id:triggerOutputs()?['body/contactid']Tracy hands the reference back on every event for that person, so a later flow can find the contact. Then save the flow.

Check it worked

The admin's test is the first proof: List interviews answers 200 with your interviews. To check a flow, run Power Automate's test on it. To test Invite participant, use an email address of your own: the invite is real, and Tracy emails that address its personal link.

Once connected, the connection is listed under Connected AI apps on your account in Tracy at Qode. Revoke it there and the flows that use it stop at once. To connect again, make a New connection and sign in again.

The answer of Invite participant says what happened. held is true when the invite was not sent yet because the interview is paused or the credits are used up.

If it does not work

Power Automate shows a 401: the connection has to be signed in again. It expired, or you revoked it under Connected AI apps. Open the connection in Power Automate, sign in to Tracy at Qode again and click Allow.
The Tracy at Qode sign-in window closes before you can click Allow, or does not open: allow pop-up windows for Power Automate in your browser, then make the connection again.
Invite participant fails with invalid_people: the contact has no email address. Put a Condition on emailaddress1 before the action when the table has such rows.
Invite participant says the invite is held: the interview is paused or the credits are used up. Resume the interview or add credits, then invite the person again.
Tracy at Qode is not among the actions: the admin imported the connector into one environment, so open the flow in that environment.

Still stuck? Write to support.

What you get

Who does what

Admin: a Power Platform admin, someone who can make custom connectors in your Power Platform environment. They import the connector once and check it by signing in. These are the steps marked Admin.

Maker: anyone who builds flows in Power Automate or Dynamics 365. They use the actions below in their flows. These are the steps marked Maker.

If you are both, do every step in order.

Four actions a flow can use

List interviews: lists your interviews. It also fills the interview dropdown of Invite participant.

Invite participant: invites one person to an interview. You pick the interview and give an email, and may add a reference of your own, such as a record ID. Tracy emails them their personal link.

Get results: reads the results of one person, newest interview session first. It needs the person's ID, which Invite participant and List events both return. A session has no write-up until its report is ready.

List events: lists what has happened in your interviews, such as a result becoming ready. Event type narrows the list and Limit caps it, from 1 to 100.

Dynamics 365 workflows are Power Automate flows, so the same connector serves both. The example flow below starts from a Dynamics 365 contact.

Before you start

A Tracy at Qode account, the one whose interviews the flows should work with, and an interview in it. If you are signed out, you are sent to sign in first.

A Power Platform environment where the admin can make custom connectors and where makers can build flows.

The connector file, tracy.swagger.json, from the integrations/power-platform folder of the Tracy at Qode project.

Steps

Admin: Open make.powerautomate.com, pick the environment, and open Custom connectors (under Data, or under More then Discover all).

Admin: Choose New custom connector, then Import an OpenAPI file. Name it Tracy at Qode and choose tracy.swagger.json.

Admin: On General, check that the scheme is HTTPS, the host is tracyinterview.ai and the base URL is /.

Admin: On Definition, check that the four actions are there. Open any of them and check that the X-Tracy-Client header has the default dynamics365 and the visibility internal.

Admin: Choose Create connector.

Admin: Open the Test tab of the connector and make a New connection. A Tracy at Qode sign-in window opens. If you are signed out, sign in there, as the account whose interviews the flows should work with.

Admin: Approve access: click Allow. The window closes and the connection is made. Then run List interviews. A 200 answer with your interviews proves the sign-in, the host and the header at once.

Maker: In Power Automate, make a flow. The example flow invites each new contact in Dynamics 365 to an interview. Start it with the Microsoft Dataverse trigger When a row is added, modified or deleted. Set Change type to Added, Table name to Contacts and Scope to Organization.

Maker: Add the action Tracy at Qode, then Invite participant. If Power Automate asks for a connection, make one the way the admin did on the Test tab: sign in to Tracy at Qode in the window that opens, then click Allow. In Interview, pick one from the dropdown, which is List interviews.

Maker: In Email, open the Expression tab and enter:concat(triggerOutputs()?['body/fullname'], ' <', triggerOutputs()?['body/emailaddress1'], '>')With a full name this reads Ada Lovelace <ada@example.com>. With no name, Tracy greets the person by the start of the address. Keep each value on one line: a line break would invite a second person.

Maker: Under Show advanced options, set Reference to the contact's id:triggerOutputs()?['body/contactid']Tracy hands the reference back on every event for that person, so a later flow can find the contact. Then save the flow.

Check it worked

The answer of Invite participant says what happened. held is true when the invite was not sent yet because the interview is paused or the credits are used up.

If it does not work

Power Automate shows a 401: the connection has to be signed in again. It expired, or you revoked it under Connected AI apps. Open the connection in Power Automate, sign in to Tracy at Qode again and click Allow.

The Tracy at Qode sign-in window closes before you can click Allow, or does not open: allow pop-up windows for Power Automate in your browser, then make the connection again.

Invite participant fails with invalid_people: the contact has no email address. Put a Condition on emailaddress1 before the action when the table has such rows.

Invite participant says the invite is held: the interview is paused or the credits are used up. Resume the interview or add credits, then invite the person again.

Tracy at Qode is not among the actions: the admin imported the connector into one environment, so open the flow in that environment.