Plan your integration

Tell us about your checkout, and get a backlog for your team: a ticket for each step of the integration, in a workable order, with tasks, acceptance criteria, and links to the docs for each step. Download it and add it to Jira, Linear, Plane, GitHub, or any other tracker. Your team estimates the tickets.

What's in each ticket

• A user story that says why the step matters to your customers or your team.
• Tasks to build, as a checklist.
• Acceptance criteria, written as Gherkin scenarios, taken from the go-live checklist and its UAT test cases.
• Dependencies, so you can see what to build first.
• Docs links to the guide section, recipe, and API reference for the step.

If you answered Not sure to a question, the tickets it affects are included, marked Decide first, with what to check before you start.

Add it to your tracker

• Markdown is one document: the epic, then each ticket. Paste each ticket into your tracker as it is, or share the document for planning.
• JSON has the same backlog as data, for a script that creates the tickets with your tracker's API.
• Copy link saves your answers in the page's address, so your team can open the same plan.

Your answers stay in your browser: nothing is sent to Teak.

Next steps

With the work planned, start building:

• Follow the integration guide step by step, from sandbox to live.
• Try the whole flow first in the quickstart, in Node.js or Python.