Does the system connect with Notion, Trello, Shopify and Stripe without a developer?

2026-11-04 | Intagya ERP

At a small distribution company, a new order arrives at ten in the morning. The clerk opens the system and records it. Then she opens Shopify and adds the customer by hand. Then Stripe, to make a payment link for the same amount. Then a line in the Slack channel that a new order came in. Then a card in Trello for the packing team.

Five windows for one order. On a day with thirty orders, a payment link gets forgotten or a card gets the wrong name, and nobody knows where it went wrong.

This is exactly what we built to stop: the system does the five steps by itself, in seconds, with the same data everywhere.

Which apps does the system connect with today?

Seventeen apps, all from inside the Automations app, with no tool in the middle:

• WhatsApp A message to the customer
• Telegram A message from your bot
• Slack A message in a channel
• Discord A message in a channel
• Microsoft Teams A message in a channel
• Google Chat A message in a space
• Twilio An SMS
• Google Sheets A row in a sheet
• Notion A page in a database
• Airtable A row in a table
• Trello A card in a list
• ClickUp A task in a list
• Asana A task in a project
• HubSpot A contact
• Mailchimp A contact in an audience
• Shopify A customer in your store
• Stripe A payment link

If you use a system that is not on the list, the Request to another system step sends the data to any link and keeps the answer for the next steps. And the Receiving link step lets any other system start an automation on your side.

What does a connection look like inside the system?

This is a real automation from the canvas for the same order story: a new sales order, then a customer in Shopify, then a Stripe payment link, then a Slack message, then a follow-up page in Notion, then a packing card in Trello.

Note the side arrow leaving the Stripe step. That is the On failure arrow. If Stripe refuses to create the link for any reason, the order is not lost quietly: the accountant gets an alert with the reason, in Stripe's own words.

Every value in the steps comes from the record itself: the customer's name, e-mail and phone, the order total and its number. You click the field in Add from the record and it lands in place, without typing any code.

Do I need a developer to add the app keys?

No. Every app gives you a key from its settings, and the step itself tells you exactly where to find it. You paste it once into the step and press Save the keys.

1. Open the other app and copy the key from the place written under the step.
2. Paste it in Keys of the app and press Save the keys.
3. Pick the values from the record: the title, the amount, the name.
4. Press Try the step on a real record, then switch the automation on.

Once saved, the key is not shown to anyone, not even to the person who saved it. Only the fact that it is saved shows. The key stays in your company's workspace alone; no other company on the system can see it.

What happens when the other app does not answer?

Outside apps go down sometimes. That is normal. What matters is what happens then.

Every outside step tries again by itself up to three times, with a pause between tries. If all of them fail, the automation follows the On failure arrow if you drew one; otherwise it shows in the run history with the full reason, and on the automations page as a step that needs your attention. You will not find out a week later from an angry customer.

Our view: put an On failure arrow on every step that involves money, such as the payment link. One alert to the accountant is cheaper than a lost order.

Why not use an outside connector tool like Zapier or Make?

They are good tools, and we respect them. But for a company that works in the system every day, the difference is large:

In practice: if your daily work is in the system, there is little sense in paying another tool to move your data from the system to your apps.

What can each department connect?

• Sales: every new opportunity becomes a HubSpot contact, and every new customer joins your Mailchimp audience.
• Accounts: every invoice makes a Stripe payment link, sent to the customer on WhatsApp and added to a Google Sheets sheet.
• Inventory: a product running low sends a Microsoft Teams message to purchasing.
• Projects: every new task gets a Trello card or a ClickUp or Asana task, for the team that works there.
• Management: a daily summary in Slack, Telegram or Google Chat, and a Notion page for every new contract.
• Store: every new customer in the system becomes a customer in your Shopify store.

What are the limits today?

We would rather say it plainly. Every app on the list has a step that sends to it: a message, a row, a page, a card, a task, a contact, a customer or a payment link. For an outside app to start an automation on your side, today you use a Receiving link that you put in that app.

The outside steps are part of full automation, switched on once per workspace, and free for the first year on yearly plans. The free plan gives you three switched-on automations with the basic steps.

Where do I start tomorrow morning?

Do not connect everything in one day. Pick the task someone copies by hand more than ten times a day; it is usually the payment link or the team message. Build one automation for it, try it on a real record, and watch the run history for a week. Then add the next step.

Read the full automations guide