Tines Academy › Lesson

Connect another service safely

Build and preview a notification for Sue’s team, then send a test message if you have a connector.

Objective: Explain what a connector is allowed to do and check a notification’s content and destination before sending it.

Let operations know about new requests

Sue’s team spends most of the day in chat, so a notification lets them know a new request is waiting without having to keep checking the tracker. Keep the message short, with enough detail to identify the request and a link to read more.

To send these notifications, the workflow needs a connector for a chat service such as Slack or Microsoft Teams. Before sending a test message, you’ll check where it will go and who looks after the connector.

Know what the connector does

A connector stores the credentials for another service. Tines 3B adds them to outgoing requests, so the workflow’s code doesn’t need to handle the password or token. Never paste passwords or tokens into chat; they’re saved with the conversation and could end up in generated code.

Before using a connector, check whose account it uses, what it’s allowed to do, and who looks after it. A message might appear to come from an app, but that doesn’t tell you how much access the connection has.

Access is managed in two places. In Tines 3B, someone decides who can use the connector. In your chat service, someone decides what the connected account or app can do. These may be different people. If you need help, start with whoever looks after the connector.

You don’t need a connector to complete this lesson. Skip the connector and test-channel setup and choose the Without a connector prompt and test. You’ll build and check message previews without sending anything. You can test delivery once you have a connector.

Give the connector only what the job needs

While you’re building, Sue’s tracker only needs to send messages to your test channel. Before team use, you’ll choose the operations channel and check that it’s the right destination. Ask whoever looks after the connector whether its permissions can be limited to those channels. They may need help from someone who manages your chat service.

Make a note of who to contact if the connection stops working. If it uses a person’s account, ask what would happen if that person left or lost access.

A draft can still send real messages to your chat service, even when you run just one step using Solo run. Use a test channel while building, and remember that anyone with access to it can see the messages. Tines 3B may ask before sending, but don’t rely on that as your safeguard.

Prepare Sue’s notification

If you don’t have a connector, go straight to Without a connector below. You can stay in your current space and check previews without sending anything.

If you’re using a connector

Open Connectors and find a connector for your chat service.

Check that you can use it in the tracker’s current space. If it’s only available in another approved space, check that you can build there and that its members are allowed to see the saved requests before moving the tracker.

Choose a test channel where the connected account or app can post and where everyone is allowed to see your test messages.

If no suitable connector is available, ask whoever manages connectors for help. You can continue with previews while access is arranged.

Don’t remove colleagues from a space or widen connector access just to finish the exercise.

Send the prompt

Choose the tab for your setup and send the prompt in workflow chat. For the connector route, fill in the connector name and test channel, or provide them when Tines 3B asks.

Prepare a chat notification for new vendor requests, using [connector] to post to [test channel]. Show the message preview and destination first. Don't send messages or turn on automatic sending until I explicitly ask.

Include the vendor, the requester and their team, the spend, the request ID and status, and a link to the list. Leave out the vendor’s email and the purchase description.

Keep the review rules and access settings unchanged, and leave the workflow as a draft.

Add a message preview for each new vendor request. I don't have a connector yet. Label each preview "Preview only" and don't send anything.

Include the vendor, the requester and their team, the spend, the request ID and status, and a link to the list. Leave out the vendor’s email and the purchase description.

Keep the review rules and access settings unchanged, and leave the workflow as a draft.

Test the notification

Start by checking the preview. Nothing should be sent yet.

Check the message

The preview should include:

Vendor name

Requester and team

Spend, request ID, and status

A link to the request list

It should leave out the vendor’s email and purchase description.

Open the list link and check that it leads to your tracker.

With a connector: send one test message

Check that the destination is your test channel. If the preview and destination are right, send this in workflow chat:

Send this preview once to the test channel we confirmed. Don't turn on automatic sending yet.

Open the channel. Check that the message arrived once and matches the preview.

With a connector: try a new request

Once that test passes, send:

Send notifications to this test channel automatically when a new request is submitted. Don't send messages for requests already in the list.

Open the request page in Browser and submit a new request with made-up vendor details.

Check that one notification arrives with the new request’s ID, details, and status.

Without a connector: check a new preview

Open the request page in Browser and submit a new request with made-up vendor details.

Check that its message preview:

Matches the new request.

Is labeled “Preview only.”

If something doesn’t match

Tell Tines 3B which request you tested, what you expected, and what happened. Ask for a focused fix, then repeat the affected check.

If a message goes to the wrong place, ask Tines 3B to turn off automatic sending before testing again.

Ask it to record unfinished checks in Readme.

What to do if something still feels fuzzy

You checked the notification’s content. With a connector, you also confirmed its destination and tested sending to the right channel. If you worked with previews, keep delivery on your list of checks before team use.

Build it safely: You learned how connectors let workflows use credentials without putting them in the code. You also learned why a working connection can still have more access than it needs. If you used a connector, you checked its permissions and whether they could be limited to the channels the tracker needs.